Which release supported installation destinations?

Mojca Miklavec mojca at macports.org
Fri Sep 14 05:12:36 UTC 2018

On Fri, 14 Sep 2018 at 06:18, Joshua Root wrote:
> On 2018-9-14 13:49 , George Plymale II wrote:
> > Also, I'm curious. You said that I'll lose the ability to get binary
> > packages. Which element of this setup causes compilation to become
> > necessary: a source-based installation or running MacPorts in a
> > non-standard prefix?
> The prefix. Our binary archives are built for the default prefix
> /opt/local and simply extracting them somewhere else often (usually?)
> won't work. That's not because of anything MacPorts does, but just
> because software that is not carefully constructed to be relocatable
> will have installation paths "baked in" in many places.

It's worth noting though that HB tries very hard to make the
majority(?) of packages relocatable. Lots of libraries would only need
a couple of install_name_tool calls. It's something that would be nice
in MacPorts as well if anyone with sufficient knowledge was willing to
work on that .


More information about the macports-dev mailing list