On Fri, Jun 30, 2006 at 03:26:15AM +0200, Goswin von Brederlow wrote:
> > Still, the buildd admin has no way to estimate how much a sub-process
> > of a package is going to use, the maintainer has at least a rough
> > idea. Since the maintainer's action is needed anyway, he can as well
> > provide this estimate.
> > And then the buildd admin can set CONCURRENCY_LEVEL to 1 to centrally
> > disable any parallelism of this kind.
> One could patch make to use concurency when the ram permits. This
> would involves checking the current ram usage and forking more builds
> if there is enough as well as suspending submakes when swapping
> starts. But i guess that would greatly complicate make itself.
And I doubt that upstream would implement this patch.
OTOH, why not use something like weak-no-auto-build or the lists for
timeouts in sbuild? That way each buildd admin could setup his own rules for
each package.
--
Ciao... // Fon: 0381-2744150
Ingo \X/ SIP: [EMAIL PROTECTED]
gpg pubkey: http://www.juergensmann.de/ij/public_key.asc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
