Hello. First of all I am not a GNOME user, but I use virt-manager-0.9.5, which depends on gtk+. Recently gnome-base/gconf-3.2.6-r1 was stabilized and this package is a dep of virt-manager. During usual "emerge -pvuDN world" I noticed that this version of gconf pulls in gtk+-3, which is not needed by any package, even by virt-manager. Of course, I simply masked gconf-3* locally and everything is fine again, but I've noticed that gconf-3* has slot "2". Shouldn't it have slot "3"? Reproducible: Always
Not really, though you accidentally brought attention to an important fact: as of 3.2.6, gtk+ dependency is redundant (it's only used by noinst examples). On a semi-related note: perhaps this could be used as an opportunity to pick up some of the few commits made in the upstream repo ? While there's always a chance upstream rolls tarball tomorrow, given gconf status, those commits may never make into an official release.
1. The slot has not changed because the library has not changed in a way that it needs a new slot. 2. the gtk+:3 dependency is disabled by simply setting USE="-gtk".
(In reply to Gilles Dartiguelongue from comment #2) > 2. the gtk+:3 dependency is disabled by simply setting USE="-gtk". As I said - that dependency is redundant now, even under a useflag. Also, do consider those commits - some are for crashers (likely rare ones, but still).
Thanks everyone for your comments.
