On Sat, Dec 03, 2005 at 11:41:38PM +0100, Frans Pop wrote: > I've tested a new base-installer with Colin's initramfs-tools patch > enabled again. As such the patch works, but I cannot see much point in > committing it currently. > Reason is that, even if initramfs-tools is already installed, 'apt-install > <kernel image>' will still pull in yaird and thus yaird will be used to > create the initrd. > Reason is that the kernel images currently list the following > dependencies: > Depends: yaird | initramfs-tools | linux-initramfs-tool, module-init-tools > I think we have 5 options: > - forget about using initramfs-tools as default for d-i > - install both even if initramfs-tools will probably not be used > - add code to edit the config file force the use of initramfs-tools; > yaird will probably still be installed though > - convince the kernel team to list initramfs-tools first instead of yaird, > effectively changing the default initrd generator > - file a bug against apt-get (?) to not pull in a first dep if an > alternative "ORed" dep is already satisfied I've never seen apt-get behave this way: the expected behavior is indeed that if initramfs-tools is installed, apt-get will not automatically pull in yaird for this ORed dependency. Can you reproduce this behavior outside of d-i? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature