Jeff Johnson wrote:

> I have multip[le issues with changes like this:
>
> 1) the patch uses envvar's
> 	Using envvar's forces remote rpm to carry an environment along
> 	in order to run remote commands, and largely forces remote  
> execution with
> 	shell. There are many times/places that macros need expansion outside
> 	of a shell environment.
>
> 2) the patch adds support for functionality that rpm itself does  
> not need or use.
> 	The number of cpu's has nothing to do with rpmbuild.
>
> 3) the patch continues to assume that a one-size-fits-all rpm  
> configurations is viable.
> 	On many if not most vendor systems, rpm configuration is  
> controlled outside
> 	of rpm itself with packages like redhat-rpm-config.
>
> But you need to find out what will happen. Perfectly understood.

I didn't like the change either, but made it more portable anyway...

My main problem is that the number of online processors doesn't
have a straight mapping over to the number of parallel make jobs
For instance, now that containers are fairly common it is regular
to have a build instance with e.g. 8 CPU but only e.g. 256M RAM.

And running "make -j8" on such a setup, quickly leads to swapping...

--anders