I use xfce & net-im/pidin & USE="-gnome". Pidgin needs gnome-base/gvfs. Starting from gvfs-1.2.*, RDEPEND have libsoup with [gnome] requirement (">=net-libs/libsoup-2.25.1[gnome]"). Using "gnome" keyword for libsoup cause many extra unused packages. Removing "[gnome]" solving this and no problems (with pidgin) found. I suggest to remove this keyworded dependece or make it more relative. Or describe why not. At least - reason of this keyword. Reproducible: Always
libsoup-gnome is needed for http/dav backend so unless you have such share mounted you won't see the difference.
*** Bug 289469 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > libsoup-gnome is needed for http/dav backend so unless you have such share > mounted you won't see the difference. > Can't you make the http backend optional under a use flag?
Not sure about that. Perhaps. Note that IUSE=gnome will go away from net-libs/libsoup soon, as we now have a libsoup-gnome package and once everything that depends on libsoup[gnome] is converted to depend on libsoup and libsoup-gnome, we have no reason for that IUSE.
(In reply to comment #4) > Not sure about that. Perhaps. > Note that IUSE=gnome will go away from net-libs/libsoup soon, as we now have a > libsoup-gnome package and once everything that depends on libsoup[gnome] is > converted to depend on libsoup and libsoup-gnome, we have no reason for that > IUSE. > For this bug the move to net-libs/libsoup-gnome doesn't do anything as gvfs will just switch to pulling that in unconditionally. The point here is to avoid pulling as much stuff as possible for people who need some applications using GNOME libs outside GNOME. One approach to consider, if the http backend is essential to GNOME functionality, is to make it a use flag that is forced on in for example gnome-light so GNOME users will always have it on.
We can either: a) Control it behind IUSE=+http Pros: - Default stays the same, people can disable it to get rid of gnome deps - Follows usual conventions for USE-flag naming Cons: - Not discoverable, have to hunt for the USE-flag pulling in gnome deps b) Control it behind IUSE=gnome/+gnome Pros: - Default stays the same for gnome users (it's in the profile) - It's obvious that this is the USE-flag pulling in gnome deps Cons: - Name does not match the feature being toggled at all I would go for (b) with a proper description in metadata.xml; something like "Enable HTTP support using <pkg>net-libs/libsoup-gnome</pkg>"
(In reply to comment #6) > > I would go for (b) with a proper description in metadata.xml; something like > "Enable HTTP support using <pkg>net-libs/libsoup-gnome</pkg>" > I think it's better to go with a. b is quite confusing in a pkg in the gnome-base category.
(In reply to comment #7) > (In reply to comment #6) > > > > I would go for (b) with a proper description in metadata.xml; something like > > "Enable HTTP support using <pkg>net-libs/libsoup-gnome</pkg>" > > > > I think it's better to go with a. b is quite confusing in a pkg in the > gnome-base category. > seems like this problem is reflected in other ebuilds too, and forcing the use of flag gnome seems useless in many of such cases. having this solved is a little step further...
Can we have a resolution on this, one way or the other? Personally I'd like to see a http useflag, not enabled by default. But I'll settle for anything as long as it is configurable.
(In reply to comment #9) > Can we have a resolution on this, one way or the other? > > Personally I'd like to see a http useflag, not enabled by default. But I'll > settle for anything as long as it is configurable. > I've added a +http USE-flag to 1.4.3 with a proper description in metadata.xml .
