Opened 11 years ago

Closed 10 years ago

#38481 closed defect (fixed)

py-gobject @2.18.0: Use unified portgroup

Reported by: cooljeanius (Eric Gallager) Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: jyrkiwahlstedt, petrrr
Port: py-gobject

Description

Right now py-gobject is actually the python24 version of py-gobject, and as such, it conflicts with py25-gobject. Using the unified portgroup should fix this. Also dbus-python24 will have to have its dependency updated accordingly.

Change History (6)

comment:1 in reply to:  description Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: mcalhoun@… removed
Owner: changed from macports-tickets@… to mcalhoun@…

Replying to egall@…:

Right now py-gobject is actually the python24 version of py-gobject,

Yes.

and as such, it conflicts with py25-gobject. Using the unified portgroup should fix this.

No, that does not explain the problem, nor does using the unified portgroup magically fix this. It's a bug unique to py*-gobject which has already been reported in #36451.

Also dbus-python24 will have to have its dependency updated accordingly.

Yes.

comment:2 Changed 11 years ago by jmroot (Joshua Root)

The py*-gobject ports don't currently use the pythonXY portgroups, which is correct because they don't have a distutils-based build system. They can be unified, but using the python portgroup isn't required or even very desirable.

comment:3 in reply to:  2 ; Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to jmr@…:

The py*-gobject ports don't currently use the pythonXY portgroups, which is correct because they don't have a distutils-based build system. They can be unified, but using the python portgroup isn't required or even very desirable.

So since they don't use the python portgroup, should they just be renamed? I kinda expected that all ports starting with py* would use the python portgroup...

comment:4 in reply to:  3 Changed 11 years ago by neverpanic (Clemens Lang)

Replying to egall@…:

I kinda expected that all ports starting with py* would use the python portgroup...

Why would they? The naming tells you it's a python module, it doesn't make any assumptions about the build system used. Take a look at the py-gobject3 port to see how this could be fixed (it uses the python portgroup and a non-distutils-based build system; it's actually the same software, just a later version).

Last edited 11 years ago by neverpanic (Clemens Lang) (previous) (diff)

comment:5 Changed 10 years ago by petrrr

Cc: Peter.Danecek@… added

Cc Me!

comment:6 Changed 10 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: fixed
Status: newclosed

The py*-gobject ports were unified in r115929, which should have fixed this problem.

Note: See TracTickets for help on using tickets.