Conflict with /Applications/MacPorts when multiple MacPorts instances installed
Rainer Müller
raimue at macports.org
Thu Jul 31 03:12:20 PDT 2008
Ryan Schmidt wrote:
> Ports that currently hardcode /Applications/MacPorts can already be
> updated to support the ${applications_dir} variable by adding this
> snippet to the port before using the ${applications_dir} variable:
>
> # Can be removed once MacPorts 1.7.0 is released
> if {![info exists applications_dir]} {
> set applications_dir /Applications/MacPorts
> }
>
> See the lisaem port for an example.
Thanks, this is a very good idea. I will change my ports in the same way.
Rainer
More information about the macports-dev
mailing list