Is gnutls the only ssl/tls implementation for vino? In that case you should use the ssl-useflag instead of the gnutls. If I specify ssl in my global USE flags I expect that every package that has optional ssl/tls functionality should have them enabled, and gnutls/nss/openssl should only be used when I want to diverse from the ebuild default (if there is more then one implementation).
there is a couple of packages across the tree doing only nss or gnutls if that's the only ssl implementation they support. I guess you will need to create a tracker bug if you want anything to be done about it.
(In reply to comment #1) > there is a couple of packages across the tree doing only nss or gnutls if > that's the only ssl implementation they support. I guess you will need to > create a tracker bug if you want anything to be done about it. > I know there are packages that does not follow this and a tracker bug may be needed for other packages, but IIRC there was a discussion a while back on gentoo-dev mailinglist about how for all packages that in some way supported optional ssl USE="ssl" should enable the default or maintainer/upstream preferred implementation and that USE="gnutls openssl nss" only should be used in conjunction with that flag if the user wanted another implementation (if avaible), since everything else is pretty confusing (and potential unsecure). Since I noticed this in your package, I decided to file a bug about it.
This looks to be the thread, but I agree with Gilles that a tracker for collecting all bugs related with this issue should be opened http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg36858.html
+ 06 Sep 2010; Pacho Ramos <pacho@gentoo.org> -vino-2.26.2-r1.ebuild, + vino-2.28.2.ebuild: + Fix gnome-keyring dependencies as reported in bug #322763 by Vicente + Olivert, also use 'ssl' USE flag instead of 'gnutls' as suggested by Xake + in bug #310683 based on + http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg36858.html . + Remove old. +
