On Wed, 14 Apr 2010 08:46:15 +0200 Justin <[email protected]> wrote: > There is at least one other example which benefits from singlular > build, atlas libs. They run a benchmark suite to create platform > specific headers, which is heavily influenced by the system load. So > having RESTRICT=parallel would make the emerge more reliable.
And that's another example of working around broken ideas. There is an uncountable number of possibilities of many different factors affecting the system load, and thus the results of the benchmark. Removing one of them would indeed help in many cases but in many other it wouldn't make any difference, additionally slowing down the whole system update process. Please notice that in order to implement that correctly, emerge would have to wait until all previously running emerges are done, and avoid running further ones while the build process is running. While in the case of xorg-server, the 'lock' is needed throughout the whole build process, in your case it is needed only for a short amount of time when the benchmark is being performed --- and the 'real' part of building would unnecessarily block emerge. If this is ever to be implemented, it totally needs to be user-overridable. Else, we'll end up someday like Windows, forcing user to reboot the system and perform the merge on a dedicated runlevel. -- Best regards, Michał Górny <http://mgorny.alt.pl> <xmpp:[email protected]>
signature.asc
Description: PGP signature
