Re: Proposed build system
On Sun, Oct 05, 2003 at 07:34:01PM +0200, Goswin von Brederlow wrote:
> Gaudenz Steinlin <firstname.lastname@example.org> writes:
> > On Sun, 2003-10-05 at 16:18, Sebastian Ley wrote:
> > > Am So, den 05.10.2003 schrieb Gaudenz Steinlin um 14:38:
> > >
> > > > The image target (which builds a floppy image) is not meaningfull for
> > > > every arch and every boot method. That i386 emulates floppys for cd
> > > > booting is a special case, not a general way of booting from cds. So if
> > > > we want to have a deb for all cases we should not only differentiate by
> > > > installation method (TYPE= cdrom, netboot, bootfloppy) but also by boot
> > > > method (cdrom, floppy, tftp, ...).
> > >
> > > Hm, I do not quite understand. We have the TYPES to roughly
> > > differentiate between the install flavours we want to provide. On
> > > different arches this may be differently implemented, this is supported
> > > by having pkg-lists, configurations and make targets variable for each
> > > architecture. If one target is not appliable for an arch at all, this
> > > target won't be built on that arch (denoted by deleting it from the
> > > Architectures: line of the corresponding package).
> > the main problem is, that the domains of debian-cd and the
> > debian-installer build system are not clearly separated. Floppy images
> > are built by debian-installer, cd-images in debian-cd. There are even
> > some targets for building cd's in debian-installer. IMO we should have
> > one build system for everything as a debian source package and build
> > some of the images (all the smaller ones) as debian binary packages.
> One question is what our requirements are for this release:
> 1. What boot methods will be supported on each arch?
> e.g. mips/mipsel doesn't need floppy, right?
> 2. How many bootable CDs will be made?
> How many of the CDs will be bootable?
> On i386 we had different boot mechanisms and kernels on different
> CDs. To me it looks like we will only have one kernel version
For powerpc, this would be :
oldpmac miboot floppy install : needs one kernel floppy + miboot,
initrd on one floppy also, but maybe a two phase installation (would
need 3 floppies) as the initrd will not fit on one floppy.
oldpmac bootx/newpmac yaboot : both will be the same, exception is
that newpmac will use yaboot, while oldpmac will give instructions on
getting and making bootx work.
chrp/chrp-rs6k builtin initrd : this one would need a initrd builtin
the kernel image, and will easily be booted from either yaboot (chrp)
or from OF directly (chrp-rs6k or pegasos).
prep : no idea, but the above method should do also.
And about flavors or installation methods, all of these need to come in
a cdrom and a net flavor, altough it would be best if one initrd can do
both, but this doesn't seem to be possible. The different methods of
booting the kernel+initrd do not influence how we will retrieve stuff
later on (udebs, base, rest of it).
As for bootable CDs, i don't know what the method is for old/newpmac,
chrp, chrp-rs6k or prep, but there is nothing such for pegasos right
now, so it will have to use OF (boot /pci/ide/cd@1,0 debian-installer).
Any comment from the reminding powerpc people ?