On 03/01/2014 16:24, Martin S. Weber wrote: > because for each new occurrence, it will have to be determined manually: > concurrency brings non-determinism with it. Many of these pkgs built > just fine (tm) for developers a, b and d (not only on, but also on multi-core > and/or SMP machines) while it didn't for devs c, f, g, and, much worse, > for users u, y and z. > > I mean, feel free to learn the sane default for (said 590) pkgs from pkgsrc, > or consider the process that spans from 2007 until now, where pkgs still are > flagged MAKE_JOBS_SAFE after the first user has run into them not building. As far as I know, MAKE_JOBS_SAFE and 'options="!makeflags"' are packaging "tricks" to work around an upstream bug. Enabling parallel builds by default would only reveal bugs, which is a good thing generally, thus I don't understand your objections. Cheers, -- Timothée Ravier
