Conflict with /Applications/MacPorts when multiple MacPorts instances installed

[Randall Wood]

/Applications is a magic location in Mac OS X. Unless your app is in
/Applications, ~/Applications, or /Network/*/Applications (I'm not
sure how the /Network domain works), certain standard Cocoa features
(like placing items in the Services menu) will be turned off in the
app. Since MacPorts sticks its apps in /Applications/MacPorts, its
apps get the standard features (Fink apps don't).

On Wed, Jul 30, 2008 at 6:18 PM, Anders F Björklund <afb at macports.org> wrote:
> Landon Fuller wrote:
>
>>> - frameworks-dir (/Library/Frameworks)
>>
>> Shouldn't this be ${prefix}/Library/Frameworks? It can still be
>> referenced with the -F compiler/linker flag
>
> I would have preferred ${prefix}/Applications and ${prefix}/Library/
> Frameworks.
> That way it is just one location to keep track of, instead of three
> (or more)...
> (Fink uses ${prefix} for Applications and Frameworks, if that is of
> any relevance)
> But it varies a bit between ports, Python uses ${prefix} while SDL
> uses /Library.
>
> --anders
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>



-- 
Randall Wood
randall.h.wood at alexandriasoftware.com

"The rules are simple: The ball is round. The game lasts 90 minutes.
All the rest is just philosophy."