Le 31 mai 2005 à 23:48, Matthew Sachs a écrit :

[snip]
The second build will use 10.4-transitional and not try to force 4.0, and will build the packages as 'nobody' instead of 'root'.
That would be good, because I've begun on 27th May and only 1120 packages have been built at the time being mostly because I should provide my password many times. 

Just a question, could it be that building as nobody changes the way some packages are built, i.e. some packages would not compile and some other ones would compile contrary to that would have happened when building as root?

For instance, it could be slightly modified to build packages as they're committed instead of doing a whole world build at once.
Would be very useful? And always from a clean tree?

It will be interesting also to have all variants of a package systematically built, if possible at all, but with a possibility to exclude some variants if they are known not to compile at a certain time (I think of ssl variants for example).

Another thing which will be useful maybe would be the possibility to introduce some other constraints, like for example, another package (not directly related) installed at the time the compilation begins, to see if it impedes or eases the compilation or the installation. I think about fortran, some freetype versions, etc in case of impeding, and about shared-mime-info, libxml2-bin, etc. in case of easing. Or for example about various gettext or ncurses versions (i.e. libgettext3 versus older gettext versions, libncursesw5 versus ncurses, idem with readline, and so on).

Another one would be to get the graph of each dependency, because the graph of all dependencies is not always easily readable.

Cheers,
Michèle


Reply via email to