Please consider preferring gnutls over openssl if both "ssl" and "gnutls" USE flags are present. The history seems to be that 2.6.0 ebuild had a fixme comment saying "Can use gnutls" - presumably ancient 2.6 GNOME release added that support to gnome-vfs. 2.6.1 ebuild added the USE flag, but preferred openssl over gnutls (probably due to gnutls support being new at that time in gnome-vfs). Sadly, this preference has carried on till now. Some reasons why gnutls should be preferred: * libsoup already uses explicitly gnutls only for ssl support - no openssl support (so full GNOME stack pulls in gnutls). * vino can use gnutls but not openssl. * neon prefers gnutls over openssl if both USE are there (not sure this is GNOME, but an outside example at least where gnutls is preferred - also gnome-vfs has imported neon sources in CVS, it seems) * gnutls takes less non-shared memory than openssl (which has libssl and libcrypto) - see http://bugzilla.gnome.org/show_bug.cgi?id=306327 for some details (this is with out-of-process applets, which is currently the case in gentoo - separate bug on that later). Sadly shared memory doesn't really count yet - something still pulls openssl in * there are no open upstream bugs for gnutls support in gnome-vfs
sounds good to me, we should probably just put this in the 2.16 overlay since it will hit unstable fairly soon.
Okay, I've updated gnome-vfs-2.15.92 in the overlay. This will get into portage when 2.16 comes out.
