Conflict with /Applications/MacPorts when multiple MacPorts instances installed

[Ryan Schmidt]

On Jul 30, 2008, at 18:44, Rainer Müller wrote:

> Joshua Root wrote:
>
>> The configure option you want is --with-applications-dir. A full  
>> list is
>> available from './configure --help'.
>
> As this option is only available in trunk, all current ports have
> "/Applications/MacPorts" and the framework path hardcoded. As of the
> next release ${applications_dir} and ${frameworks_dir} can be used in
> Portfiles instead. Until then, there is no easy solution to keep
> multiple MacPorts installations.

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.