/Library/Frameworks violates layout
N_Ox
n.oxyde at gmail.com
Tue Nov 6 07:01:04 PST 2007
Le 6 nov. 07 à 07:05, Juan Manuel Palacios a écrit :
>
> So, do we have an agreement on this? Any objections to turning on
> warnings against /Library/Frameworks in the upcoming MacPorts 1.6?
> I support to move to discourage writing to that directory, gcc's -F
> flag should allow any application needing a framework to look for
> it under prefix, just as Anders makes it clean in his message. Any
> reason why we *shouldn't* move our frameworks into prefix?
>
> And as for macports1.0, we can still rely on configure's --with-
> tclpackage flag to place it inside prefix in customized installations.
>
> Regards,...
>
>
> -jmpp
>
> <snip>
Does --with-tclpackage add some tcl code to the beginning of the port
executable to add the path to ${auto_path}?
--
Anthony Ramine, the "Ports tree cleaning Maestro".
<nox at macports.org>
More information about the macports-dev
mailing list