> > Ideally we'd have a massively parallel cluster of Amigas, Macs and Ataris
> > to do that. Right now, we'd be more than happy if additional machines
> > (real or emulated) could take up some of the backlog at times. We'd need
> > to prevent an emulated system attempting to build a CPU intensive package,
> > and for that we'd need a build time estimate up front. Not implemented
> > yet.
>
> Hmmm, sort of...
> http://unstable.buildd.net/index-m68k.html shows some rough build time
> estimation for all packages in needs-build:
Well, what we'd need is twofold: a way to query that database for the
estimated build time of package X, and a way to correct for the various
build speeds on different hardware, for the time estimate to be
meaningful.
I'm sure you can provide query access easily. Normalization of build time
needs to be done from scratch, perhaps.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
