diff options
| author | Sam James <sam@gentoo.org> | 2025-12-04 01:41:54 +0000 |
|---|---|---|
| committer | Sam James <sam@gentoo.org> | 2025-12-04 01:44:46 +0000 |
| commit | fa5ca61883ac6e2931a1caeab96018ab9a7a4755 (patch) | |
| tree | a8135e6a547d79dd3fee89e14399ef245b9da1bb /dev-python/async-timeout/async-timeout-5.0.1.ebuild | |
| parent | 23e0f39f781c2d6f0ba1fa8d7611ea84c66a2c1f (diff) | |
| download | gentoo-fa5ca61883ac6e2931a1caeab96018ab9a7a4755.tar.gz gentoo-fa5ca61883ac6e2931a1caeab96018ab9a7a4755.tar.bz2 gentoo-fa5ca61883ac6e2931a1caeab96018ab9a7a4755.zip | |
net-libs/nodejs: use eninja for jobserver support
Switch back to using eninja directly, not emake->ninja. Calling ninja
indirectly has a few disadvantages, as we have to both pass -Onone to
bypass Portage's default for output synchronisation, it means we have
to hack around not having options passed down to ninja, and it breaks
jobserver support (because ninja won't act as a client if -jN is passed).
We started using emake in 9825cd3d791456cd0265d0c82611c4ceffd4ff22 to avoid
ninja-utils (not clear to me why) but since 305e66472660ee50117267b499f23d3883340deb
we already use ninja-utils again, so the indirection gains us nothing.
With this, nodejs + the steve jobserver doesn't bomb my machine with
jobs anymore.
Closes: https://bugs.gentoo.org/966651
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-python/async-timeout/async-timeout-5.0.1.ebuild')
0 files changed, 0 insertions, 0 deletions