On 2007-December-18 , at 20:15 , Daniel J. Luke wrote:
On Dec 18, 2007, at 2:10 PM, Daniel J. Luke wrote:
On Dec 18, 2007, at 2:06 PM, Daniel Oberhoff wrote:
Hmm, so how does the port command actually know where it's tree
lives?
Is it hardcoded? Or does the installation put a tag somewhere on
the system?
${prefix} is set when macports is installed and it's put in that
conf file.
it's also populated in the macports_autoconf.tcl file.
if you didn't build with --with-tclpackage set so that your two
installs have separate package directories, that could be causing
your problem.
Hi, could you elaborate a bit on that. I have the exact same problem
with:
- two macport trees: /opt/local/ installed as a regular install and /
opt/local-exp installed from source with --prefix=/opt/local-exp/
- no ~/.macports
- the sources in both ${prefix}/etc/macports.conf are pointing to the
correct location
and still the port command in /opt/local/bin/port lists the content
of /opt/local-exp/
Thanks in advance.
JiHO
---
http://jo.irisson.free.fr/
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
