Comment 9 for bug 1440504

Revision history for this message
Barry Warsaw (barry) wrote :

So maybe this isn't as difficult as I first thought. The basic idea is that instead of putting both the libpythonloader and libpython3loader shared libs in the same binary package, I'm creating two new binary packages libpeas-1.0-0-python2loader and libpeas-1.0-0-python3loader.

Each of this will only contain the respective .so. Thus libpeas-1.0-0*.deb will have no Python dependency at all, and the split binaries will only have the appropriate libpython2.7 or libpython3.5 dependency.

Then we'll need to update the Depends of the packages mentioned above, by adding:

* deja-dup - libpeas-1.0-0-python3loader
* eog-plugins - libpeas-1.0-0-python3loader
* gedit(-dev/-plugins) - libpeas-1.0-0-python3loader
* gnome-core-devel (for libpeas-dev): libpeas-1.0-0-python2loader
* gtranslator: libpeas-1.0-0-python2loader
* liferea: libpeas-1.0-0-python2loader
* totem-plugins/libtotem0: libpeas-1.0-0-python3loader
* rhythmbox (and many friends): libpeas-1.0-0-python3loader

I don't think any of the other libpeas binary packages need splitting.

I'll attach the patch for libpeas. Could someone on the desktop team please let me know if this is sane, and if so, could you shepherd the necessary changes (for this and the dependents) into Debian and Ubuntu as appropriate?