2 ms·
Using ~/.local gives you all those things without giving root access, there is no good reason to stick everything in /usr/local especially with something like n
by tomxor 7y ago
Using ~/.local gives you all those things without giving root access, there is no good reason to stick everything in /usr/local especially with something like npm which is wide open for anyone to publish anything instantly.
- inimino 7y agoYes, and then the question is, should you be putting programs you don't trust at all in your PATH?
- tomxor 7y agoYes, if i trust them enough to add and not replace binaries.
- inimino 7y agoBut once you run any of those binaries, it's free to replace any of your other (non-root-owned) binaries in `~/.local`. So the trust you're talking about seems to be a preference, but I don't think there's any particularly plausible threat model that makes one of these safer than the other.