>>>>> "edward" == Edward Avis <[EMAIL PROTECTED]> writes:
Hi
edward> To be really slick: if a package fails, your script could randomly
edward> install some extra packages on the machine (perhaps 50% at random of the
edward> total packages in Cooker) and try again to build. If that succeeds,
edward> remove some packages and try again, etc. By a kind of binary search you
edward> would find the minimal set of packages needed, and those could be added
edward> to the spec files as BuildRequires lines.
Instead of that, it is easier, to convince the script to search
through .h and .c files for #include<> and search what -devel packages
provide that.
edward> Once all the dependencies are correct, it wouldn't take long to just
edward> verify that things work whenever a new package is released, just as a
edward> kind of sanity check. It might be good for Mandrakesoft to dedicate a
edward> fairly old, slow box to doing this 24 hours a day - getting the latest
edward> uploads to Cooker, uninstalling everything except essential packages and
edward> what's mentioned in BuildRequires, trying to build it, sending mail to
edward> the maintainer if it fails.
Compiling the kernel in one Athlon 1200Mhz with 512MB of RAM
(i.e. everything is in RAM, the disk that you have doesn't matter)
takes more than 1 hour. Any old machine will not support that very
well :( But yes, that is a good idea, just not an slow machine.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
