[Nix-dev] Re: Another approach at parallelizing in-build jobs

[Jeff Johnson]

On Jun 20, 2010, at 6:41 PM, Marc Weber wrote:

> Excerpts from Jeff Johnson's message of Mon Jun 21 00:27:14 +0200 2010:
>> Or do I still miss something?
> You're right.. It doesn't make sense to pass
> N=1, N=10 or N=8 or N=4 to the builder because you'd get 4 different hashes
> 
> However you can map it to a boolean values:
> 
> POTENTIALLY_BAD = N > 1;
> 
> This way you have what you want: You separated the maybe bad packages
> from good ones.
> 
> This POTENTIALLY_BAD could also be used to non chroot builds etc.
> 

Here's an old hacker's rule:

	Never check a return code you don't know how to handle.

There's lots of ways to screw up a build, "make -jN" is just one.

Or do you have a formal proof that "make -jN" for some build MUST succeed?

There's all sorts of foolishness in "POTENTIALLY_BAD" as a boolean imho.

But feel free to do whatever.

(aside)
Getting "make -jN" into RPM was just as hard ... 

73 de Jeff