I demand that Steve Langasek may or may not have written... [snip] > One of the worst contributors to the use of 'script' in upstart jobs > instead of 'exec' is the need for backwards-compatibility with pre-upstart > /etc/default/* files. The options here are all fairly poor: > > - ignore the admin's /etc/default settings when switching init systems > - migrate any local changes to /etc/default into the upstart job at > upgrade time, by editing a conffile in a maintainer script > - keep sourcing /etc/default at runtime
> I guess systemd has largely chosen option 1 (in part because there's a > weird view in the systemd community that these jobs belong upstream, so > Debian integration issues are entirely ignored). For many upstart jobs in > Ubuntu, we've chosen option 3. Which do you think is the right solution? > Are there other options I haven't seen? Of those listed above, I'd agree with option 3 or some optimisation of it – option 2, modified to do the migration at runtime if /etc /default/foo has been modified since last seen, would cover that, I think. [snip] -- | _ | Darren Salt, using Debian GNU/Linux (and Android) | ( ) | | X | ASCII Ribbon campaign against HTML e-mail | / \ | http://www.asciiribbon.org/ disassembler: n. An unattended five year old child. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/526e4e6180%li...@youmustbejoking.demon.co.uk
