* Matthias Julius (lists@julius-net.net) wrote: > Eric Dorland <eric@debian.org> writes: > > > * Matthias Julius (lists@julius-net.net) wrote: > >> Eric Dorland <eric@debian.org> writes: > >> > >> >> - If you set up the alternatives in preinst, then there is a time when > >> >> the symlink exists but the pointed binary hasn't been unpacked yet -> > >> >> unbootable system. > >> >> - If you set up the alternatives in postinst, there is a time when there > >> >> is no /sbin/init at all -> unbootable system. > >> > > >> > The second case is only true if the init providing packages conflict > >> > with each other, which I don't think would necessarily be the case. > >> > >> It would also be true if the admin chooses to deinstall tho old > >> package and install the new package at the same time. > > > > Sure, but then they are explicitly taking that risk. > > Yes, but probably without being aware of it. > > How do you tell them about it before the old init package is removed? Maybe some sort of prerm check, but why bother? Someone installing alternative init systems is probably knowledgeable enough. -- Eric Dorland <eric@kuroneko.ca> ICQ: #61138586, Jabber: hooty@jabber.com 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6
Attachment:
signature.asc
Description: Digital signature