On Saturday, Dec 7, 2002, at 15:27 US/Eastern, [EMAIL PROTECTED] wrote:
Instead of trying to pass the compiler make flag into make itself --
something that just about every planet on the package has a note in
the README of 'you can try parallel make if you want, but if it
breaks, turn it off'-- why not build packages in parallel, if the
developer so desires.
If a particular package is known to support parallel makes, it should
[optionally -- it may be wise to still provide a DIFFERENT setting to
turn it on/off] add the -j flag, etc, internally. This should not be
something applied to all packages on a global basis -- it will cause
problems!
As long as package A and package B do not depend on each other and, in
cases where there isn't a version conflict, even if they do depend on
each other, then why not allow A and B to built at the same time.
I frequently do this when building. I check to make sure stuff will
have no extra effects on each other, then I might run them at the same
time. For example, I might build kdegames3 and abiword at the same
time.
The only additional support needed in Fink [I believe] would be the
ability to detect the dpkg lock such that the install of one of the
packages won't abort if the other already has the lock....
Yea, this pops up occasionally.
b.bum
Kyle Moffett
-------------------------------------------------------
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
