Move GConf depends to a seperate binary
Bug #1550896 reported by
Julien Lavergne
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Debian) |
Fix Released
|
Unknown
|
|||
pidgin (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Currently, gconf on pidgin is only used to retrieve proxy settings from GNOME. It puts an hard depends on gconf, even if pidgin is used on a non-gnome environment. Also, it seems that this feature may be broken (see LP #878032 and https:/
The included debdiff move away the gconf files to a pidgin-gnome binary, so people not using GNOME can remove the gconf depends.
tags: | added: patch |
Changed in pidgin (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in pidgin (Debian): | |
status: | Unknown → New |
Changed in pidgin (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Thanks, I don't think it's worth splitting to another binary. The depends was useful at the time where the schemas registration was done on installation but isn't really needed nowadays with the triggers use
there doesn't seem to be an easy way to get dh_gconf to not add the depends though, some suggestions (sorted of by somewhat order of preference)
- create a new dh_gconf flag to not add gconf to up misc:Depends and get piding to use it
- hack around in debian/rules (e.g move the schemas away before dh_gconf is called and move it back before the deb is packed so the misc depends is not added)
- don't use misc:Depends in control (I think nothing else get added at the moment, but it feels wrong and might be of use for other things later)
- don't install the schemas (it's only used by programs using libgnome, which is deprecated for ages and only to handle custom url like <protocol> ://<contact> , in practice very few users are likely to hit those case if ever)
I would be happy to sponsor one of those changes, let me know what you think