Alakazam wrote:
> On 17 mai 08, at 23:09, Rainer Müller wrote:
> 
>> Alakazam wrote:
>>> The question of MacPorts still being universal after a selfupdate  
>>> is  indicated as being open.
>> No, MacPorts is not being build universal on selfupdate.

> 
> Even if the +universal variant is added to all ports in variants.conf  
> (I can imagine this is completely unrelated) ?

Currently that does not affect MacPorts base. port selfupdate calls a 
hardcoded ./configure command.

For the future it would be good if MacPorts itself would use its own 
port, so that 'port selfupdate' would become the same as 'port sync && 
port upgrade MacPorts'.

> Then transferring MacPorts from one machine to another is going to be  
> a bit more complex than simply transferring /opt/local ?
> 
> Any suggestions on how to do this properly so that "port list  
> installed", which might be useful on the secondary mac, still works  
> correctly ?

port archives would be a possibility. But at the moment it is not that 
easy to build archives. We had a discussion lately on that topic, see 
"Manual Install" started by Simon Wheatley [1].

Rainer

[1] Message-Id: <[EMAIL PROTECTED]>
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to