[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:                |
---------------------------+--------------------
Changes (by kencu):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 nobody said it was because of your gcc build.

 almost all compilers are written to look in /usr/local by default, as
 above

 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).

 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.

 MacPorts’ policy is that it doesn’t support users having anything
 installed in /usr/local for thiscreason.

 There is no way to work around it in base or in portfiles.

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