conflict between "portA +python33" and "portB +python33"
mojca at macports.org
Mon Apr 7 06:24:58 PDT 2014
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
when the same python variant is selected for both ports.
More information about the macports-dev