Opened 12 years ago
Closed 11 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 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | mcalhoun@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to mcalhoun@… |
comment:2 follow-up: 3 Changed 12 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 follow-up: 4 Changed 12 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 Changed 12 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).
comment:6 Changed 11 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The py*-gobject ports were unified in r115929, which should have fixed this problem.
Replying to egall@…:
Yes.
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.
Yes.