On Thu, Mar 20, 2014 at 7:59 PM, Burton, Ross <[email protected]> wrote: > On 20 March 2014 19:01, Laszlo Papp <[email protected]> wrote: >> This init script is adding support for sysv and no more. This is also >> indicated in the first line of the commit message. I am sorry, but I >> will not test it systemd and with other systems > > You're not being asked to test with systemd. You're being asked to > add LSB-standard sysvinit-specific headers to a sysvinit script.
In my understanding, people were referring to two issues: 1) not working with systemd and what not compat modes. This is not something I will test any soon. 2) It is not consistent, whereas if I take a look into busybox, the consistency is what I do, apparently. I would like to quote from the Fedora wiki for instance: "LSB Headers are not required for Fedora SysV-style initscripts, but they may be used. There is no requirement in the LSB certification for any system scripts to be LSB compliant, and it can cause issues with ordering." So what is wrong about it without systemd and other compat modes? If it is that big a deal (i.e. blocker), perhaps it is better to document it in the contribution guideline as a generic trap. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
