On Nov 30, 2015, at 2:58 AM, Andrea D'Amore wrote: > The same things that would happen if, say, I manually copy > TextEdit.app as /Applications/MacPorts/MacVim.app and then try to > install the macvim port. The other two scenarios can happen even more > easily without explicit trickery.
But MacPorts "owns" /Applications/MacPorts and /opt/local. It is a user error to install things into those directories via a method that is not MacPorts. Whereas /Library/Fonts is owned by the user and the user is right to expect to be in control of its contents. > As it turns out the system (or Cocoa at least) recursively scan the > font folders, so adding system-wide port fonts in > /Library/Fonts/MacPorts doesn't seem anything different that what's > already being done. Oh great, /Library/Fonts/MacPorts sounds like a fine place then. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
