Re: Bug#225465: debian-policy: packages must give choice to not start at boot, via debconf
Vincent Bernat <firstname.lastname@example.org> writes:
> OoO Pendant le journal télévisé du lundi 29 décembre 2003, vers 20:45,
> John Hasler <email@example.com> disait:
>> . /etc/default/package # this contains "RUN_package_AT_BOOT"
>> test -z "$RUN_package_AT_BOOT" && echo $0 | grep -q '^S' && exit 0
This sort of thing is still a terrible idea; as has been noted
earlier, if you answer "don't start at boot" to the debconf question,
it makes it impossible to run '/etc/init.d/package start' afterwards
(since then the init.d script sees /etc/default/package says to never
> After an upgrade, the package will be started, even if it is not
> running. There is no improvement over not making symlinks in
Didn't invoke-rc.d(8) solve this problem? Or isn't it supposed to?
The man page suggests that 'invoke-rc.d package start' does nothing if
there's not an S??package link in the current runlevel's rcN.d
Really, with the default tools, we have a perfectly good way for users
to disable a daemon at boot time ('rm' and 'ln -s' to reenable it). I
can think of ways in which the current situation isn't ideal, but
adding a debconf question to every package that starts a daemon is
kind of ridiculuous, and wastes users' time when installing packages
(or a new system).
David Maze firstname.lastname@example.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell