Unified Python portgroup
Jeremy Lavergne
jeremy at lavergne.gotdns.org
Thu Jan 10 15:06:08 PST 2013
>>> [...] "python.versions 25 26 27". To my surprise the
>>> following command was accepted:
>>>
>>>> [root at lampje] Code/macports/py-pdfrw# port install subport=py32-pdfrw
>>>> ---> Computing dependencies for py32-pdfrw
> [...]
>>>> ---> Configuring py32-pdfrw
>>>> ---> Building py32-pdfrw
>>>> ---> Staging py32-pdfrw into destroot
>>>> ---> Installing py32-pdfrw @0.1_1
>>>> ---> Activating py32-pdfrw @0.1_1
>
>> Unexpected, I should think. I'd also check that the files installed are actually for python32:
>> port contents py32-pdfrw
>
> Yes, they are:
>
>> [root at lampje] Code/macports/py-pdfrw# port contents py32-pdfrw
>> Port py32-pdfrw contains:
>> /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw-0.1-py3.2.egg-info
>>
> [...]
>
> I don't see this as a big issue, but perhaps a warning is in order.
I suspect this is restricted to the current directory "subport=..." command.
When building portindex, the unnamed versions aren't created so users won't ever stumble upon them.
More information about the macports-dev
mailing list