move oldfolder newfolder results in oldfolder/newfolder

[Bradley Giesbrecht]

On Feb 16, 2012, at 11:41 AM, Ryan Schmidt wrote:

> On Feb 16, 2012, at 13:34, Bradley Giesbrecht wrote:
>> 
>> Only py24-cairo fetches 1.4.12 sources. The other pyxx-cairo ports use different sources.
>> There are a total of 4 sources for py-cairo and 6 suports. Notice that py2[67]-cairo subport distfiles have the numeral "2" in py2cairo.
>> 
>> pillbox:dports brad$ sudo port distfile name:^py[\\d]*-cairo$ | grep -E -- "--|\["
>> --->  Distfiles for py-cairo
>> --->  Distfiles for py24-cairo
>> [pycairo-1.4.12.tar.gz] /opt/local/var/macports/distfiles/py-cairo/pycairo-1.4.12.tar.gz
>> --->  Distfiles for py25-cairo
>> [pycairo-1.8.2.tar.gz] /opt/local/var/macports/distfiles/py-cairo/pycairo-1.8.2.tar.gz
>> --->  Distfiles for py26-cairo
>> [py2cairo-1.10.0.tar.bz2] /opt/local/var/macports/distfiles/py-cairo/py2cairo-1.10.0.tar.bz2
>> --->  Distfiles for py27-cairo
>> [py2cairo-1.10.0.tar.bz2] /opt/local/var/macports/distfiles/py-cairo/py2cairo-1.10.0.tar.bz2
>> --->  Distfiles for py31-cairo
>> [pycairo-1.10.0.tar.bz2] /opt/local/var/macports/distfiles/py-cairo/pycairo-1.10.0.tar.bz2
>> --->  Distfiles for py32-cairo
>> [pycairo-1.10.0.tar.bz2] /opt/local/var/macports/distfiles/py-cairo/pycairo-1.10.0.tar.bz2
> 
> Ok. Different subports having different versions is unfortunate but sometimes necessary I suppose. I don't understand the different distnames... What if anything is the difference between pycairo-1.10.0.tar.bz2 and py2cairo-1.10.0.tar.bz2?

pycairo stopped supporting python24 at 1.4.12, python25 at 1.8.2, changed the name to py2cairo for python2[67] and changed the name back to pycario or python3[12].


>>> Note that when you begin work on multiple subports of a single port, only the first subport's work directory is symlinked into the port's directory. To find the others, you'll have to dig into /opt/local/var/macports/build. If you want a particular subport's work directory to be symlinked into a port's directory, make sure all of that port's other subports have been cleaned first.
>> 
>> This explains what I am seeing.
>> So a subport cannot be reliably built without performing a clean to ensure worksrcpath does not contain source for other subports?
> 
> What I said applies only to the work symlink, which is only created for your convenience as a maintainer (and can indeed be turned off entirely in macports.conf); it does not affect how the port builds or the worksrcpath.


Thanks for refreshing my knowledge. I need to consider this when doing common things like ./work/portname/configure --help.


Regards,
Bradley Giesbrecht (pixilla)