[MacPorts] #71583: Multiple ports opportunistically use whatever they find in /usr/local

[MacPorts]

#71583: Multiple ports opportunistically use whatever they find in /usr/local
---------------------------+--------------------
  Reporter:  barracuda156  |      Owner:  (none)
      Type:  defect        |     Status:  closed
  Priority:  Normal        |  Milestone:
 Component:  base          |    Version:  2.10.5
Resolution:  invalid       |   Keywords:
      Port:                |
---------------------------+--------------------

Comment (by barracuda156):

 Replying to [comment:4 kencu]:
 > what I meant was that an uncertain amount of software you built would be
 tainted by references to /usr/local, so that is macports doesn’t
 distribute user’s builds of software ( which people have asked for even
 very r3cently).

 MacPorts manages to distribute broken software regardless, since this is
 not the only way to have something broken, and by far not the worst way.
 As long as some folks keep committing directly to the master without any
 testing, a lot of stuff will be broken.

 > by the way, because of this software you had in /usr/local all this
 time, especially oldvparts of R, any port you have ever written, tested,
 or debugged becomes suspect, as nobody can ever know how that has affected
 your builds now.

 Well, LOL

 Since there is no feasible way to know what ''you'' have on your machine,
 the same applies to whatever you have written, tested or debugged just as
 much.

 However, one does not need to have anything in `/usr/local` to get
 opportunistic linking of all kinds, it is sufficient to have standard
 MacPorts’ ports. If you want to avoid that, prohibit installing any ports
 from source as long as non-dependencies are active. Because pretty much no
 one tests this properly or even checks configure args, a lot of ports are
 potentially broken for any given user.

-- 
Ticket URL: <https://trac.macports.org/ticket/71583#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS