3 ms·
Very bad idea, and one that will cause a lot of breakage. There’s a reason every package management system on Mac uses its own prefix.
by teilo 8y ago
Very bad idea, and one that will cause a lot of breakage. There’s a reason every package management system on Mac uses its own prefix.
- sigfubar 8y agoWhat are you talking about? I've been using a similar homegrown setup for many years and never had any issues. In fact, I've come to appreciate being able to write directly on my Mac shell scripts destined to run on Linux boxen in production.
- fabiomaia 8y agoI had a similar goal I guess: make my dotfiles, scripts and workflow the same across macOS and Linux. :)
- fabiomaia 8y agoI understand things can break, but I have yet to run into such issues. Specifically, what exactly can break by replacing e.g. coreutils with GNU's?
- twblalock 8y agoI haven't ever broken macOS doing stuff like that, and I've been doing it for years, with both Macports and Homebrew. I use the default prefix and make sure the Homebrew stuff is in my $PATH before the built-in stuff and it works fine.