Long time listener, infrequent poster... Chris Leishman wrote:
<snip>
But if you are specifically targeting the "common" user are they really likely to be building from source at all, wouldn't the "common" user be using the binary dists for the majority of their packages? So then the "common" user for this particular set, are the very people who would want CPU saturation because they are also the people more likely to have a dual box, or they are just gluttons for punishment and have been building from source on linux, BSDs, and are used to the slow down.
However, this is all working on the assumption that totally saturating the CPU is desired behavior. This is true on dedicated build machines, but I would strongly suggest that it's NOT the case for the majority of fink users. The small gain obtained by saturating the CPU with multiple makes is outweighed by the unresponsiveness of the system in general. Most users are not going to be willing to close every other application and leave their machine alone while it compiles for periods of up to several hours (qt3, kde, etc).
I like this because it sounds like a good feature anyways, not necessarily because it specifically handles this discussion.
If developers really think that parallel compiling would be useful for them, then there should be an option in fink to control it's usage.
http://danconia.org
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
