[MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

[MacPorts]

#47755: Broken symlink left by select code when selected port is deactivated causes
poppler and other ports using aclocal to fail during configuration.
-----------------------+--------------------------------
  Reporter:  lukasz@…  |      Owner:  macports-tickets@…
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  base      |    Version:  2.3.3
Resolution:            |   Keywords:
      Port:            |
-----------------------+--------------------------------

Comment (by m74z00219@…):

 Replying to [comment:19 ryandesign@…]:
 > Replying to [comment:18 m74z00219@…]:
 > > I tried removing the symlink to wxwin.m4, but install still fails. I
 think my problem extends to the fact that I've been fooling around with
 git (from macports). The log refers to a list of items that were not
 installed by Macports...or at least not registered to have been installed
 by Macports.
 > >
 > > Actually, after uninstalling some git repo related stuff (sudo make
 uninstall), I was successfully able to install encfs -- thanks!
 > >
 > > Is this typical of git repo project installations to interfere with
 Macports?
 >
 > The method of software distribution (i.e. from a git or hg or svn or cvs
 or bzr repository, or from a tarball download) should have no bearing on
 whether a project interferes in some way with MacPorts. You'll have to be
 more specific about the problem you're experiencing, if you still need
 help with it, but it sounds like it's not related to this ticket, and if
 it's something you're doing outside of MacPorts (using "`make`" for
 example) then it sounds like it's not related to MacPorts.

 While my original ticket (#48052) was rightly marked duplicate, it turned
 out that my inability to install encfs was two-fold. The broken /
 unregistered symlink from wxWidgets and Git project compilations.

 You're right on that it was the "making" that caused the issue, so in
 certain respects the conflicting software was my fault. That said,
 Macports does host a Git port, which is a software distribution platform.
 There is no indication / warning that Git projects involving compilation
 may install libraries that might interfere with Macports. In my opinion,
 this echos the debate happening above regarding the dividing line between
 user and maintainer responsibility.

-- 
Ticket URL: <https://trac.macports.org/ticket/47755#comment:21>
MacPorts <https://www.macports.org/>
Ports system for OS X