moving "macports1.0" to ${prefix}

[Boyd Waters]

+1 from me, FWIW...

I've made my MacPorts completely self-contained and this helps.

(Along the same lines, I've changed all my Python ports to install  
under ${prefix}/lib, and other things to install under ${prefix}/ 
Applications -- multiple, parallel binary distributions are required  
and we keep *everything* installed by our MacPorts under a *single*  
directory tree.)

- boyd

Boyd Waters
National Radio Astronomy Observatory
Socorro, New Mexico



On Aug 16, 2007, at 3:15 AM, Anders F Björklund wrote:

>
> For MacPorts 1.6, it might be a good idea to consider moving  
> "macports1.0" from the current @TCL_PACKAGE_DIR@ directory to the  
> @prefix_expanded@/share/macports/Tcl directory, in order to make  
> the MacPorts installation self-contained within the designated  
> prefix ?
>
> If the "macports1.0" module needs to be in the system's Tcl package  
> directory in order for other (inferior) software to find it, then  
> can't this be accomplished by setting up a symbolic link ? e.g. / 
> Library/Tcl/macports1.0 -> /opt/local/share/macports/Tcl/macports1.0
>
> --anders
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-dev