Two MacPorts installs: problem with Python

[Bart Masschelein]

>> How can I get around this? I don't think deactivating the Python  
>> from my
>> original MacPorts will solve the problem.
>
> When you install from source, and want to avoid conflicts with a  
> standard
> MacPorts install, use the --with-tclpackage, --with-applications- 
> dir, and
> --with-frameworks-dir to point to subdirectories within your chosen  
> prefix.
> This way, everything gets placed into ${prefix}; for example,
>
> $ ./configure --prefix=/other --with-tclpackage=/other/Library/Tcl
> --with-applications-dir=/other/Applications
> --with-frameworks-dir=/other/Library/Frameworks

Thanks, that was what I needed.

>> PS: I use the trunk, because the tarball for 1.7 gave me consistent
>> errors about 'violation of the path structure' for each port. This  
>> was
>> solved by using the trunk.
>
> Probably ticket #13789
>
> <http://trac.macports.org/ticket/13789>
>
> which as you've discovered is fixed on trunk.  If it is that, you  
> should be
> able to still use 1.7 just make sure there's no slash at the end of  
> prefix.

Thanks, I will remember this when I use the tarball in the future.  
Will the tarball reflect this change in the future, for a minor  
version update?

Cheers,

Bart