![]() ![]() The command would look something like asciinema rec -c "./mydemoscript.sh" myrecording. Specifically, I'll be using asciinema for the recording with the -c flag (see here), and demo-magic.sh for the automated typing, since it supports waiting for commands to finish executing (or not) and custom wait times on top of that. What I'm planning on doing for a project I'm in is to use both asciinema as well as demo-magic.sh. Rather than fighting idiomatic go practices.I've searched for a lot of solutions for my own projects, and this is the solution that I've come up with: My solution: Limit the "command line instructions" to: I gather it's distributed as an archive in order for the Changelog, Readme and License to be available - but as it's all downloaded from github anyway, it's hard to see why that really matters (rather than just have -h spit out a link or two).Īs, if you're using a normal, full-featured web browser, there's no way of knowing if what you select, is what you copy and then paste - it would probably be better to just link directly to the latest binary release for the various platforms (linux32, linu圆4, linux-arm, OSX 32bit, OSX 64bit) - and let the user save the binary somewhere. In this case, it seems like a lot of effort to get a tgz-archive just to download a single executable. Put it in ~/opt with xstow, and add ~/opt/bin to your path, ~/opt/man to your man-path, ~/opt/include, ~/opt/lib. But why would you need to demand all users of your system (even if that's just system users) also trust it? And in this particular case, the app has access (by design) to your terminal, so yeah, you need to trust the app a bit. You typically need root to write to the system dirs (/usr/* /bin etc). It's pretty rare for an app to need root privileges. Any suggestions on the topic are welcome! There are few of them out there so if anyone can point me to any "proven/reliable" one I'd appreciate that. I'm thinking about using one of these services which auto-build deb/rpm, they host them as apt/yum repos etc. curl/sh sucks on many fronts but I made sure the script doesn't get executed when partially downloaded and it's not "| sudo sh". "First download this script, then review it, then run it" is not that hard but most people wouldn't review the script anyway, and those who would are the ones who are doing that now anyway. ![]() For all other distros (and people wanting new version right now) you can curl/sh which is equally easy. Next thing is: "apt-get install asciinema" or "brew install asciinema" is awesome because it uses your software package manager and it's a single command. So time (or lack of thereof) is one thing. Sure, these guys do this too in their spare time and they don't owe me anything.īut when seeing this I'm like "oh boy, packaging is hard, I don't have time for dealing with this". Let's not get into "Go packaging" discussion again, but what you can see in the mentioned Gentoo thread there's always some problem (no vendoring is bad, vendoring is bad). That's fine.īut there are also situations like this: There are no packages for other distros, but we'll never be able to provide ones for all distros (unless we're very popular project with lots of contributors). I maintain Arch Linux one (while not using Arch for more than few years now) but this one's usually ready on the release day. There are 2 nice guys who maintain the first two packages, doing great job, but it always takes time until the packages are ready (we're all doing it in our spare time, and there's process, especially Fedora case, which you can't skip). There's also homebrew package and Arch Linux one (aur). Let me describe you the situation.Īt the moment there are native packages for Ubuntu/Debian (ppa) and Fedora/CentOS (in core repo). "Piping shit into sh" is not really great way to do it, I fully agree. This is something I have been fighting with in my head for quite a while. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |