split out gconf bindings

Bug #60615 reported by Jani Monoses
14
Affects Status Importance Assigned to Milestone
gnome-python (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Gconf is used by several python programs (gnome-app-install, update-manager, onboard)
Even if they do not use other gnome libraries besides gtk, these are brought in because the python bindings are all in a single package. This affects CD space and bandwidth for
people willing to install such app in non-gnome environments.
It is more logical to have separate packages for .so-s which do not depend on eachother.
It can be done step by step, so this patch only separates gconf. Bug 30173 is related and
could be solved if this one goes well.

Revision history for this message
Jani Monoses (jani) wrote :

debdiff against current package

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank for your bug. We will split the package if Debian does it too, other way we would make distributions not compatible, could you summit the patch to Debian?

Changed in gnome-python:
assignee: nobody → desktop-bugs
importance: Untriaged → Wishlist
status: Unconfirmed → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Note that splitting a package has a transition cost so you probably want to split gconf and gnomecanvas in the same update rather than having gconf splitted first and then some other component

Revision history for this message
Jani Monoses (jani) wrote :

I'll let the debian maintainers know as well. As for transition costs, it's easier because there'
s one less upload to do, but what other transiion costs are there? Packages depending on
p-g2 still get gconf so all current packages should work without being touched.
As for canvas, I thought that maybe that is deprecated since there's goocanvas (even though it is still used)

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: [Bug 60615] Re: split out gconf bindings

Le samedi 16 septembre 2006 à 17:35 +0000, Jani Monoses a écrit :
> I'll let the debian maintainers know as well. As for transition costs, it's easier because there'
> s one less upload to do, but what other transiion costs are there?

right, in the case python-gnome2 keeps depending on python-gconf there
is no transition to do

Revision history for this message
Jani Monoses (jani) wrote :

Updated debdiff: fix example install paths, split out gnomecanvas as well.

Jani Monoses (jani)
Changed in gnome-python:
importance: Wishlist → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

This upload fixes the issue:

" gnome-python (2.16.0-0ubuntu3) edgy; urgency=low
 .
   * debian/control.in:
     - Build-Depends on xvfb (used to run "make check" on build)
   * debian/control.in, debian/python-gnome2.examples,
     debian/python-gnome2.install, debian/python-gnomecanvas.examples,
     debian/python-gconf2.examples, debian/python-gnomecanvas.install,
     debian/python-gconf2.install:
     - Patch by Jani Monoses <email address hidden>:
     - "Split Gconf and GnomeCanvas bindings to separate packages."
       (Ubuntu: #60615)
   * debian/control.in:
     - fixed Conflicts, Replaces versions to use for the split
   * debian/control.in, debian/python-gconf.examples,
     debian/python-gconf.install:
     - name the gconf package python-gconf, no need of versionning
   * debian/rules:
     - run "make check" on build (Ubuntu: #28789)
"

Changed in gnome-python:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.