Dropping recommendation to install system headers / command line tools

Ken Cunningham ken.cunningham.webuse at gmail.com
Wed Jul 5 16:28:49 UTC 2017


> 
> Yea, compilers that assume /usr/local must be searched for include files are broken. Other than that, what else is the issue?
> 
>

I wasn’t around for it, but I think in the beginning /opt/local was chosen for macports in part because /usr/local was being heavily used by darwinbuild and they needed to keep away from that.

Also, other installers tend to dump things in there by default and overwrite things.

Years went by. darwinbuild is rarely used. homebrew decided to go for /usr/local, and accept the occasional dump in there by some installers. macports was already invested in /opt/local, and stayed there.


IF you have stuff in /usr/local you may not have problems for some times — but then one day, you will try to install something with macports, and you will get a failure you can’t sort out. You’ll post a ticket, somebody will eventually figure out you have polluted /usr/local, ask you to empty it out, and your macports build with then succeed.

And then you go down -100 points on the “macports” index :>

Ken


More information about the macports-dev mailing list