3 ms·
> Brew never had this problem because they chose a sane path How so? Taking over /usr/local as Homebrew does is guaranteed to cause conflict. Using a dedicated
by pulisse 6y ago
> Brew never had this problem because they chose a sane path
How so? Taking over /usr/local as Homebrew does is guaranteed to cause conflict. Using a dedicated file hierarchy as Nix does is quite reasonable and there's nothing magical about rooting it at /.
- ryanianian 6y agoHow does it "take over" /usr/local? You can still `./configure --prefix=/usr/local` on your own software and things continue to work as long as you're not installing the same thing that brew is.
- masklinn 6y ago> How does it "take over" /usr/local? Because it shoves all its shit there without asking. Macports actually did it correctly and IME never had any issue.
- xyproto 6y agoInstalling several versions of the same piece of software is central to Nix. While locking all needed versions for a specific application provides stability, I can't believe it doesn't come without a large increase of complexity, especially in connection security upgrades which triggers other libraries to need an update as well.