The ebuild for gnome-base/gnome-2.22.3 contains dependencies on both gnome-base/gvfs and gnome-base/gnome-vfs. Both do the same thing, although gnome-vfs is deprecated in favor of gvfs. If a particular part of Gnome depends on gnome-vfs still, I understand having that particular ebuild contain a reference to gnome-vfs. However, it is beyond me why the Gnome meta-ebuild still pulls it in. Reproducible: Always Steps to Reproduce: 1. Open /usr/portage/gnome-base/gnome/gnome-2.22.3.ebuild in your favorite text editor. 2. Search for gvfs. 3. Search for gnome-vfs. 4. Cry loudly. Actual Results: Both gnome-vfs and gvfs are found. Expected Results: gnome-vfs should no longer be there; it is deprecated and logically should only be included in programs that still need it, as opposed to the meta-ebuild for Gnome as a whole.
(In reply to comment #0) > If a particular part of Gnome depends on gnome-vfs still, I understand having > that particular ebuild contain a reference to gnome-vfs. However, it is beyond > me why the Gnome meta-ebuild still pulls it in. Because http://download.gnome.org/teams/releng/2.22.3/versions says so. And because applications in the gnome meta in turn also depend on gnome-vfs, but only the minimum required - the meta makes sure you at least have the minimum suggested for that particular whole GNOME release. The gnome-vfs atom will be removed from gnome meta if either of the following becomes true: 1) Upstream release engineering team doesn't list it as a GNOME component for that release; or 2) No non-USE flag dependent package listed in the gnome metapackage depends on gnome-vfs So you will get gnome-vfs anyway, but at least get suggested to upgrade a newer version if you don't use --deep thanks to the GNOME meta, whereas for individual packages we have a unwritten policy to only depend on the minimum necessary. This is a definite WONTFIX for 2.22.3 due to the above, sorry.
