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

Re: Using buildds only

On 8/25/05, Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> wrote:
> Olaf van der Spek <olafvdspek@gmail.com> writes:
> > On 8/23/05, Marc Haber <mh+debian-devel@zugschlus.de> wrote:
> >> On Tue, 23 Aug 2005 01:42:18 +0200, Martin Pitt <mpitt@debian.org>
> >> wrote:
> >> >Something like this is in fact considered. Probably Ubuntu won't use
> >> >pbuilder itself since it is not the most efficient implementation
> >> >around, but rebuilding the buildd chroots from scratch would help to
> >> >eliminate many FTBFS bugs due to polluted chroots.
> >>
> >> Surely you are aware how much time it takes to rebuild a chroot on
> >> slower architectures. Some technology able to restore a large
> >> directory tree to a static default in short time should be used here.
> >
> > What causes this long times? Slow IO?
> Slow disks, slow/little ram, slow cpu. Restoring a chroot at 1MB/s
> will take minutes.

I guess this is all related to IO though?
Why don't you extract the files to another place and then simply
link/unlink them instead of tar/rm?
> But what is 5m to copy a clean chroot compared to the 60m to install
> all the kde Build-Depends for a huge build and another 60m to remove
> them again because one libs version isn't high enough to build
> anything?
> Also one doesn't need to do this every time, spreading the restore
> time over multiple compiles makes that rather small per package.

Reply to: