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

[Christopher D. Ramos]

>
> Yes, that is what I was saying, where, again, by "git project", you mean
> "some software project that just so happens to do its development in a git
> repository". The use of git is incidental to the problem.


Heh, I think I finally see where we are talking pass one another. I
wholeheartedly agree with this: "some software project that just so happens
to do its development in a git repository."

That said, I don't think it's merely incidental. After all, git is, in a
sense, part of the Macports ecosystem by virtue of a version of it being
hosted by Macports. Is there not a policy about hosting ports -- whether
version control or other types of software distribution mechanisms -- that
may distribute projects that ultimately harm a Macports installation?

My reason for bringing up "/opt/local" was because I was wondering if there
was a chance that the makefile of some git project (or any other project
management system!) might instruct it (implicitly or explicitly) to install
under /opt/local. And if so, how could this be systematically avoided.

I was assuming that you had already resolved the original problem from the
> ticket referenced in the subject line, by removing the now-broken
> symlink(s) "port select wxwidgets" had created on your system (if you
> haven't done that yet, then you should do that now), and were encountering
> a new problem specific to this software you downloaded and built.


You assumed correctly! Those aforementioned instructions worked, though
only in concert with uninstalling libraries installed by certain git
projects. I carried on though because I had assumed that getting rid of
that symlink broke wxmaxima. Well, at least the ability for it to be
summoned directly from command line.

If there really is no practical or meaningful way for this to move forward,
I'm prepared to drop my concerns!


Christopher D. Ramos

LinkedIn <https://www.linkedin.com/in/chrisdavidramospaxperscientiam>

Pax Per Scientiam <http://www.paxperscientiam.com>

Public Key
<http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EAD11447DF2D80A>


On Tue, Jun 23, 2015 at 6:08 PM, Ryan Schmidt <ryandesign at macports.org>
wrote:

>
> On Jun 23, 2015, at 4:13 PM, Christopher David Ramos wrote:
> >
> >
> >>
> >> There is no inherent conflict between MacPorts and any given
> >> software downloaded with git. Rather, there is (apparently, from what
> >> you've told us) a conflict between MacPorts and the specific software
> >> you downloaded with git, but that conflict would have been present
> >> regardless of how you downloaded the software; it has nothing at all
> >> to do with git. Git is just a program that lets you download things.
> >> It has no knowledge of whether those things you download are going
> >> to conflict with other parts of your system.
> >
> > You are paraphrasing what I just said.
>
> Not intentionally.
>
> >
> > My understanding is that Macport ports install there own libraries under
> > the path prefix "/opt/local/" so as to prevent conflicts with and
> > reliance out of date Apple libraries.
>
> Well yes. I mean, MacPorts needs to install itself *somewhere*, some
> prefix. Bad choices for prefix would be /usr (that's where Apple installs
> stuff) and /usr/local (that's where compilers look for dependencies by
> default, and is where users expect to be able to install software
> manually). A good choice is therefore anywhere else. We chose /opt/local.
>
> > Are you saying that it was only a
> > fluke that a git project would have built files into Macports created
> > directories?
>
> Yes, that is what I was saying, where, again, by "git project", you mean
> "some software project that just so happens to do its development in a git
> repository". The use of git is incidental to the problem.
>
>
> I was assuming that you had already resolved the original problem from the
> ticket referenced in the subject line, by removing the now-broken
> symlink(s) "port select wxwidgets" had created on your system (if you
> haven't done that yet, then you should do that now), and were encountering
> a new problem specific to this software you downloaded and built.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20150623/c7f0deb1/attachment.html>