Re: python nproc vs MAKE_JOBS issues

[David Holland <dholland-pkgtech%netbsd.org@localhost>]

On Mon, Nov 11, 2024 at 07:43:56AM -0500, Greg Troxel wrote:
 > >> Maybe we should simply fix the default in py-maturin, once. This is a
 > >> philosophical disagreement about whether a tool should consume all CPU
 > >> resources by default, or by default use one, and take a -j flag.  go is
 > >> similarly troubled.
 > >
 > > maturin already has a -j flag and I don't think we should change it to
 > > '-j1' by default - that will be a surprise for maturin users coming
 > > from other environments.
 > 
 > Then it should be in the TOOL_DEPENDS wrappers somehow.  It does not
 > seem reasonable to have to open-code this in every pkgsrc user.

There should also be a system-level way to get a default answer to
"how many jobs should I spawn?" since this arises with everything that
parallelizes (not just build tools) and both 1 and NCPUS are bad
fallbacks.

-- 
David A. Holland
dholland%netbsd.org@localhost