[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Integrating the debian-installer into the archive

Anthony Towns <ajt@debian.org> writes:

> On Sun, Oct 05, 2003 at 07:55:01PM +0200, Geert Stappers wrote:
> > Our (di-team) current approach is to hide^Wput the images[1] in
> > a dot deb package and worry some later time how to make the
> > binaries[1] available.
> It's probably a bad idea to make it a .deb.
> I'd strongly recommend you not try to get the buildds doing this until you
> can demo the scripts in a reliable way. Presumably you want to directly
> access the archive to pull down various udebs, eg, which isn't something
> you can necessarily do on buildds in a straightforward manner.

All buildds should have /etc/apt/sources.list (inside the chroot)
setup to point to a reasonable mirror. The D-I build automtically uses
the same source.

If they don't the build would fail and that can be easily fixed.

> Have you got the scripts working for all arches yet, or just i386? Are
> you sure that the scripts are going to work automatically, without root
> privleges, on other architectures?

Someone claimed that all Buildds are compiling as root anyway. But
either way works fine.

> > We are looking for a way to generate the binaries on all archs as
> > none-debs and an integration method with the debian archive.
> I'm not entirely clear on what you're saying, btw - the language
> barrier and all. Please include examples of what you're talking about,
> and consider attaching or linking to the scripts you're talking about.

The problem isn't the building of the files. That either works or
gives a build failure which can then be fixed. (Which would already be
a big advantage [to see it fail and how].)

The problem is how to get the build floppy images, tftp images, cdrom.iso
images into ftp.debian.org automatically. Encapsulating them in a deb
would make it automatic but noone realy likes that.
Just adding the files to the changes files would probably get them
uploaded through the normal queue and then the ftp scripts don't know
what to do with them.

The goal is that a debian-installer.deb is uploaded, the buildd crunch
away and then files appear in /debian/dists/sid/disks-<arch>/.

Is disks-<arch> the right name if we include the small cdrom images?


Reply to: