[64683] trunk/dports/devel
Eric Le Lay
elelay at macports.org
Sat Mar 20 01:00:12 PDT 2010
Hi,
only gmpc and glade3 depend upon ige-mac-integration.
gmpc doesn't use the python bindings, so it's safe.
glade3 does however provide a python25 variant and a quartz variant
(depending upon ige-mac-integration).
Those variants will conflict if ige-mac-integration is upgraded to python26.
In turn, only gnome-developer-tools depends upon glade3 and it has no
dependents.
What is difficult is to simultaneously build python25 and python26
bindings. But I propose to add a python26 variant to ige-mac-integration
and register it as conflicting with python26. This is not too difficult.
Of course, the combination glade3+python25+quartz plus
ige-mac-integration+python26 will be broken...
Le 19/03/10 14:33, Ryan Schmidt a écrit :
>
>
> On Mar 15, 2010, at 13:55, Eric Le Lay wrote:
>
>> Hello Ryan,
>>
>> thanks for your remarks !
>>
>> this ports is essentially a gtk library.
>> It provides python bindings but only targeted at one version.
>> I managed to build both python25 and python26 bindings this week-end, but it is only by calling "make" and "make install" again in a post-destroot hook, with a long list of overriden variables. Not the most elegant code.
>>
>> I'll also have to handle all the combinations of python25 and python26 variables.
>>
>> I also figured that it would make it easier to express dependencies in python26 ports on py26-ige-mac-integration and in python25 ports on ige-mac-integration.
>>
>> I had probed the maintainer of ige-mac-integration by email about a py26 version but never got an answer. Maybe my email was eated by his spam control software.
>>
>> Only three-some ports dependents on ige-mac-integration so maybe upgrading ige-mac-integration to python 2.6 is the best way.
>>
>> I'm seeking your advice here.
>
> If you can test those three ports that depend on ige-mac-integration and verify that they work even when it's updated to python 2.6, then yes I'd recommend that approach.
>
> Don't forget to Reply All.
>
>
>
>
More information about the macports-dev
mailing list