upgrades fail after leopard update

[Alan Batie]

Cameron Simpson wrote:

> Breaking cycles doesn't turn it into a tree, but fortunately that's ok;
> an acyclic digraph is fine - you can traverse it like a tree and just
> need to avoid rebuilding a package you rebuilt on another path. Which
> macports seems to do just fine anyway.

If it looks like a tree... ;-)
You would probably redundantly check a port, but the following times 
around, it would match as current, so nothing would be done.

> As remarked, it would be good to distinguish chosen variants from
> auto-variants in the port install state information.

I'm not familiar with the variant options (I usually just say "port 
install something" and if it doesn't work, curse ;-) and manually 
install it), but yes, I can see where someone may choose to force a 
non-standard version and that would need to be tracked.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3263 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080612/e59c259f/attachment.bin