> I guess Homebrew could come up with its own cute little appellation — /usr/pkg or somesuch — /opt/homebrew would be a somewhat traditional place to put it.

> I guess Homebrew could come up with its own cute little appellation — /usr/pkg or somesuch — /opt/homebrew would be a somewhat traditional place to put it. > but then you run into that other lovely little POSIXism where every application has its own way of calculating a PATH, such that you’d need to add that /usr/pkg directory to an unbounded number of little scripts here and there to make things truly work. What? You should be able to add it to the system PATH that's set for sessions and call it a day on a POSIX system. PATH is an environment variable and inherited. If MacOS is in the habit of overriding PATH on system scripts I have to imagine that's because they completely screwed it up at some point in the past. Generally, you just add it to your use session variables in whatever way your system supports (.profile, etc) if you want it for your user, or at a system level if you want it system wide (I could see maybe Apple making this hard). The only times in over 20 years I've ever had to deal with PATH problems are when I ran stuff through cron, because it specifically clears the PATH. More recent systems just specify a default PATH in /etc/crontab for the traditional / and /usr bin and sbin dirs. Maybe you're thinking of the shared library path loading? That should also be easily fixed.