Re: [announce] s6-linux-init-0.0.1.0
On 2015-06-19 19:19, Les Aker wrote: Looks like s6-linux-init 0.0.1.0 pulls s6 in as a build-time dependency. Not a huge issue, but might be worth updating the docs to clarify that until the next release removes that? I've learned to trust your docs and build tools enough that I spent a while hunting for what I was doing wrong :) Actually, the docs provided with the 0.0.1.0 tarball would tell you that :) I changed the dependencies in a later git commit, and updated the online docs to match that commit, but it means they don't match the 0.0.1.0 release anymore. My apologies for the misdirection here. That's an interesting question: should the docs match the latest versioned release or the latest git commit ? There are pros and cons for both. Anyway, please use the latest git, it comes with a few other fixes in addition to removing almost all build-time deps. Also, I'm in favor of making the shebang use bindir Also done in the latest git. -- Laurent
Re: [announce] s6-linux-init-0.0.1.0
Looks like s6-linux-init 0.0.1.0 pulls s6 in as a build-time dependency. Not a huge issue, but might be worth updating the docs to clarify that until the next release removes that? I've learned to trust your docs and build tools enough that I spent a while hunting for what I was doing wrong :) Also, I'm in favor of making the shebang use bindir; in the past, I've hit issues with some packaging validation tools that check shebangs to make sure the desired files exist (namcap in particular). Not the end of the world if you keep it at the current, but would save me some scripted regexing - Les
Re: [announce] s6-linux-init-0.0.1.0
On 18/06/2015 05:12, Guillermo wrote: I did a quick run and found out that in generated execline scripts except the stage 1 init, the shebang line starts with #!execlineb. Yes (unless you use slashpackage). And on the machines where I tested, it's not a problem as long as execlineb is in the PATH - the kernel still finds the binary. This is certainly nonstandard, and surprised me, but I saw it work, so since the package is Linux-specific anyway, I didn't change it. I can change it to bindir if it doesn't work on some configurations, though. -- Laurent
Re: [announce] s6-linux-init-0.0.1.0
Hi, 2015-06-17 17:27 GMT-03:00 Laurent Bercot: s6-linux-init-0.0.1.0 is out. It is a new package that, for now, only contains one program, and more documentation than source code. :) Its goal is to automate the creation of stage 1 (/sbin/init) binaries for people who want to run s6-svscan as process 1. Nice! Bug-reports and suggestions welcome, especially since it's still brand new and probably rough around the edges. I did a quick run and found out that in generated execline scripts except the stage 1 init, the shebang line starts with #!execlineb. If I'm not mistaken, it's because the EXECLINE_EXTBINPREFIX macro (from execline/config.h) is being used, which, unless the execline package has been configured with the --enable-slashpackage option, expands to nothing. The bindir variable should be used instead, I suppose. Thanks, G.
[announce] s6-linux-init-0.0.1.0
Hello, s6-linux-init-0.0.1.0 is out. It is a new package that, for now, only contains one program, and more documentation than source code. :) Its goal is to automate the creation of stage 1 (/sbin/init) binaries for people who want to run s6-svscan as process 1. Unfortunately, it has to be system-specific; this is the Linux version because it's the OS I know the best. However, it is very possible to run it, examine the created scripts, and adjust them to another system's idiosyncrasies. http://skarnet.org/software/s6-linux-init/ git://git.skarnet.org/s6-linux-init Mirrored on github as well. Enjoy, Bug-reports and suggestions welcome, especially since it's still brand new and probably rough around the edges. -- Laurent
