Daniel,
It seems like a chicken and the egg problem here with UseMaxBuildJobs.
If the feature is considered entirely optional, it is difficult to rationalize
using it in larger packages that beg to be built with parallel make whenever
possible. Also, one can argue that there is inconsistent behavior currently
in fink. If one does a clean installation from fink cvs, the UseMaxBuildJobs
is automatically created in fink.conf for the user. I am only saying that
this behavior should be extended to existing installations of fink when
fink itself is upgraded as well. It is difficult to see how one can say
it is okay to silently create UseMaxBuildJobs for a fresh install of fink
without warning the user but that this is inappropriate for existing
installations of fink. They should be treated identically regarding the
autocreation of UseMaxBuildJobs in fink.conf.
Jack
ps Ny view is that if the user objects to UseMaxBuildJobs, they could set
it to 1 and, since UseMaxBuildJobs now exists, fink will never mess with
UseMaxBuildJobs in fink.conf again. I am only worried about the fact that
few if any users will expend the effort to discover this new option and
manually create it themselves.
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
