Thanks for the answer. Here is my comments for the different solutions : - New dh_gconf : it's seem a bit overkill, especially if pidgin is the only one to use it. And I don't know dh enough to make this change in the near future :-)
- hack on debian/rules : probably a good idea, but I don't think I can make it clean with cdbs - don't use misc:Depends : yes, it feels wrong. If something else use this feature in the future, it will not be obvious to re-enable it in the package (most of packages have misc:Depends). - Considering it's seems broken, and used for a very limited use cases, I think it's safe to just remove it. I attached the updated debdiff. ** Patch added: "pidgin_2.10.12-0ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1550896/+attachment/4587016/+files/pidgin_2.10.12-0ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1550896 Title: Move GConf depends to a seperate binary Status in pidgin package in Ubuntu: New Status in pidgin package in Debian: New 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://developer.pidgin.im/ticket/13867). The included debdiff move away the gconf files to a pidgin-gnome binary, so people not using GNOME can remove the gconf depends. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1550896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
