macports-dev@lists.macosforge.org writes:
>Revision
>[ http://trac.macosforge.org/projects/macports/changeset/30721 ]30721
>Author
>[EMAIL PROTECTED]
>Date
>2007-11-05 10:01:13 -0800 (Mon, 05 Nov 2007)
>
>Log Message
>
>use_bzip2 default to 'no';
>document 'use_parallel_build';
>
>
>Modified Paths
Mark Duling writes:
>One question about "use_parallel_build". Do you think that keyword
>relates to a phase, or should it be considered a "global keyword"? I
>thought perhaps "global", or do you consider it specifically related to
>the build phase? I thought parallelism applied more generally to
On Nov 5, 2007, at 2:30 PM, [EMAIL PROTECTED] wrote:
Perhaps I was influenced by my recollections that some ports stop
installing outside of the build phase until another port is finished
installing. At least I think I've seen this.
you have.
If that is so and a ports
hangs at activate or an
"Daniel J. Luke" <[EMAIL PROTECTED]> writes:
>> Perhaps I was influenced by my recollections that some ports stop
>> installing outside of the build phase until another port is finished
>> installing. At least I think I've seen this.
>
>you have.
>
>> If that is so and a ports
>> hangs at activate
I've just added a way to automatically set the number of build jobs
(if desired):
If the number of build jobs is set to "0" (in the config file), the
number of jobs is set to the number of cores.
This works only on Mac OS X (and FreeBSD -- though untested).
-Markus
On 05.11.2007, at 20:32,
