Re: [opensuse-factory] python-gobject and python3-gobject

On 08/19/2013 09:23 AM, Dominique Leuenberger a.k.a. Dimstar wrote:

Quoting Todd Rme :

...

Currently python-gobject in the devel:languages:python and python3-gobject in devel:languages:python3 are separated into two packages.

I consider this the error :)

Not if you have around 1200 packages to maintain in a single project :-) Anyway, I explained the reasons elsewhere, so let's go on.

...

However, python-gobject is linked to the version on openSUSE:Factory, which still has python 2 and python 3 spec files in one package. Its devel project is GNOME:Factory, which also still has both spec files.

The devel project being G:Factory is absolutely right and expected; the version is closely linked to the entire GNOME Stack and, as we used to have the devel projects defined in d:l:* before, it was increasingly painful to update the entire GNOME:Stack => python-gobject depends on up-to-date packages in G:F and other packages in G:F depend on python-gobject; both only see each other once forwarded to Factory.

Hence, the adjustment of the devel project to G:F (d:l:* does not mean it has to be devel project for everything python).

as replied already on packaging, fully agreed and nothing to add.

...

This is leading to frequency breakage in the devel:languages:python version, since it links to a package that has two spec files while it only has one. If we are going to go with the separate packages we should to it in factory as well.

Fix the links in d:l:p and use the correct names. the fact that this was split in d:l:p does not mean it has to be done.

And I really wonder what's the issue here. GNOME:Factory is the devel project and openSUSE:Factory links to it, period. devel:languages:python / python-gobject is a branch to GNOME:Factory / python-gobject similarly to devel:languages:python3 / python3-gobject. This way, both only build the spec file they're interested in besides having both as part of the sources. This comes naturally through the _link and doesn't hurt anyone. If someone really wanted, he could just create a project.diff for each branch to drop the other spec file.

...

It would be easy to provide a submit request for this. However, currently python3-gobject in openSUSE:Factory and GNOME:Factory are linked to their respective python-gobject packages, so doing the submission now would break python3-gobject.

I would decline it, sorry. I am the person mostly maintaining those packages and am certainly not willing to maintain the same code twice; as long as building py3 and py2 variants of the same package is less effort than maintaining two variants, I will stick with this. Once the differences emerge to be too big, of course, this will be revised.

...

So if we are going to go with the separate python2 and python3 packages, can we do so for python-gobject as well? If not, we need to either unlike python-gobject from factory, go back to using two spec files, or remove it from devel:languages:python entirely (which may not be a bad idea since it often depends on the latest GTK version anyway).

I agree to the last point: remove it from d:l:p => there is nothing you can really gain from having it; as mentioned: it is an integrated part of the GNOME stack and is in sync with the versions.

Just that we have other Python packages depending on it which you may not want to get maintainership handed over for. Take python-keyring as a prime example to depend on either/or Gnome / KDE bits. BTW. that's the same reason why we have python-qt4 in d:l:p. It's not just because I like it to be there ;-) -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)