How does MacPorts locate "moved" ports?

[Jeremy Lavergne]

> 	I'm trying to install something that has py26-ipython (among others) as a dependency.  This has been moved in the Great Unification to py-ipython.  How does MacPorts go about satisfying this dependency?  How does it know where to look?
> 
> 	I ask because I'm in process of forcing a downgrade to an earlier version of iPython so that Spyder will continue to work.  Spyder doesn't work with versions of iPython at or later than version 11 (the current version), though the new spyder-beta (hopefully) does.

You're correct the Great Unification swallowed up the other ports, and they exist within the py-ipython portfile now. That one portfile defines several versions, specifically:
    python.versions     24 25 26 27 31 32

When the index of all the ports is run, it finds all these "subports" and continues to indicate them as usual. The trick you want to do is set the version and epoch for specific subports (it looks like the 24 and 25 versions already have differing versions). There are code blocks like those that you want to use/create.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 8796 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20111101/42bc9710/attachment.bin>