conflict between "portA +python33" and "portB +python33"

[Mojca Miklavec]

On Mon, Apr 7, 2014 at 3:44 PM, Jeremy Lavergne wrote:
> The active_variants PortGroup can be used this way:
> active_variants $depspec $required $forbidden
>
> That forbidden section is likely what you’re after, inside a variant block.

Oh, sure, thank you for reminding me (of something that I should have
known already) ;)

Mojca


> On Apr 7, 2014, at 9:24, Mojca Miklavec <mojca at macports.org> wrote:
>
>> What is the most reasonable way to declare a conflict between "portA
>> +pythonXY" and "portB +pythonXY"? The ports themeselves don't conflict
>> and different python variants don't conflict either (portA +python33
>> and portB +python34 works OK).
>>
>> The problem is that both ports install files with the same name to
>> $prefix/Library/Frameworks/Python.framework/Versions/X.Y/lib/pythonX.Y/site-packages
>> when the same python variant is selected for both ports.
>