2 ms·
So what you can do, though, is not link them in and your scripts can use their Homebrew directory to get ahold of the GNU binaries. It is still a script change
by eropple 6y ago
So what you can do, though, is not link them in and your scripts can use their Homebrew directory to get ahold of the GNU binaries. It is still a script change you have to make, but it's one you can make at a top level and then your bash wranglers are very unlikely to break them.
(Though I use those as daily-driver packages on Macs and have actually never had something break? GNU tools tend to support BSD options.)
- xmodem 6y agoMaybe this is easier with the way homebrew does things (I prefer MacPorts) but then you have to manage a bunch of symlinks to bring in the stuff you DO want to use by default. I actually hadn't thought to try this approach, though. The next time this happens I will definitely give it a shot.
- eropple 6y agoHomebrew does collate them all in a couple of directories for you, yeah.