Re: Arch-dependent extra packages for debian-cd

2004-03-27 Thread Thiemo Seufer
Santiago Garcia Mantinan wrote: > > > - Is is ok to have bootloaders for i386 listed but not for others? > > I think that most bootloaders are pulled in by debootstrap, so appear on > > tasks/base-sarge. lilo and grub are an exception as debootstrap installs > > neither. > > Anyway, this boot load

Re: Arch-dependent extra packages for debian-cd

2004-03-27 Thread Thiemo Seufer
Petter Reinholdtsen wrote: > [Thiemo Seufer] > >> Yes, until recently debootstrap installed lilo. > > > > AFAIK this change was for all architectures. So all bootloaders will > > have to be added explicitly now (for their relevant architecture). > > No, the changes wasn't done for all archs. But

Re: Arch-dependent extra packages for debian-cd

2004-03-27 Thread Petter Reinholdtsen
[Thiemo Seufer] >> Yes, until recently debootstrap installed lilo. > > AFAIK this change was for all architectures. So all bootloaders will > have to be added explicitly now (for their relevant architecture). No, the changes wasn't done for all archs. But I believe it _should_ be done for all ar

Re: Arch-dependent extra packages for debian-cd

2004-03-27 Thread Thiemo Seufer
Joey Hess wrote: > Thiemo Seufer wrote: > > AFAIK this change was for all architectures. So all bootloaders will > > have to be added explicitly now (for their relevant architecture). > > As far as I can tell it was only for i386. alpha, ia64, > m68k, powerpc, sparc, mipsel, hppa, all still have

Re: Arch-dependent extra packages for debian-cd

2004-03-26 Thread Joey Hess
Thiemo Seufer wrote: > AFAIK this change was for all architectures. So all bootloaders will > have to be added explicitly now (for their relevant architecture). As far as I can tell it was only for i386. alpha, ia64, m68k, powerpc, sparc, mipsel, hppa, all still have boot loaders listed in deboot

Re: Arch-dependent extra packages for debian-cd

2004-03-26 Thread Colin Watson
On Fri, Mar 26, 2004 at 09:34:13PM +0100, Thiemo Seufer wrote: > Joey Hess wrote: > > Thiemo Seufer wrote: > > > > I think that most bootloaders are pulled in by debootstrap, so appear on > > > > tasks/base-sarge. lilo and grub are an exception as debootstrap installs > > > > neither. > > > > > >

Re: Arch-dependent extra packages for debian-cd

2004-03-26 Thread Thiemo Seufer
Joey Hess wrote: > Thiemo Seufer wrote: > > > I think that most bootloaders are pulled in by debootstrap, so appear on > > > tasks/base-sarge. lilo and grub are an exception as debootstrap installs > > > neither. > > > > Didn't this change recently (or was that only for cdebootstrap)? > > Yes, un

Re: Arch-dependent extra packages for debian-cd

2004-03-26 Thread Joey Hess
Thiemo Seufer wrote: > > I think that most bootloaders are pulled in by debootstrap, so appear on > > tasks/base-sarge. lilo and grub are an exception as debootstrap installs > > neither. > > Didn't this change recently (or was that only for cdebootstrap)? Yes, until recently debootstrap installe

Re: Arch-dependent extra packages for debian-cd

2004-03-26 Thread Santiago Garcia Mantinan
> > - Is is ok to have bootloaders for i386 listed but not for others? > I think that most bootloaders are pulled in by debootstrap, so appear on > tasks/base-sarge. lilo and grub are an exception as debootstrap installs > neither. Anyway, this boot loaders should only be listed in the i386 arch,

Re: Arch-dependent extra packages for debian-cd

2004-03-26 Thread Thiemo Seufer
Joey Hess wrote: > Thiemo Seufer wrote: > > When adding the kernel/bootloader packages for mips/mipsel in > > debian-cd I found some probably arch-dependent packages were on > > this list unconditionally. The appended patch is my best guess > > about it, but I'm not sure about some issues: > > > >

Re: Arch-dependent extra packages for debian-cd

2004-03-26 Thread Joey Hess
Thiemo Seufer wrote: > When adding the kernel/bootloader packages for mips/mipsel in > debian-cd I found some probably arch-dependent packages were on > this list unconditionally. The appended patch is my best guess > about it, but I'm not sure about some issues: > > - Is discover actually needed