So, from a technical standpoint, that’s the correct answer (well, I’d use ionice -c3 nice -n20 make -j$(nproc)).
But…I kind of feel that most of the time, if someone is likely to be asking an upstream project for a binary installer, it might not be a great idea for them to be installing non-package-managed stuff systemwide. I don’t know if they’d be in a good position to diagnose or fix issues arising from that. Maybe use something like alien.
I’d be less-concerned about compiling to and invoking locally from the compilation directory, something that most packages permit for.
So, from a technical standpoint, that’s the correct answer (well, I’d use
ionice -c3 nice -n20 make -j$(nproc)).But…I kind of feel that most of the time, if someone is likely to be asking an upstream project for a binary installer, it might not be a great idea for them to be installing non-package-managed stuff systemwide. I don’t know if they’d be in a good position to diagnose or fix issues arising from that. Maybe use something like
alien.I’d be less-concerned about compiling to and invoking locally from the compilation directory, something that most packages permit for.
./configure make -j$(nproc) ./build/bin/app<thumbs up>