dev-libs/libgdata: tests: don't remove https testing if libsoup is new enough

The issue was identified to be with older libsoup, so only revert the TLS
patch if available libsoup is buggy for the test. Next libgdata release will
fix it properly (grabbing the upstream fix verbatim would mean unnecesary
eautoreconf)

Package-Manager: Portage-2.3.4, Repoman-2.3.1

diff --git a/dev-libs/libgdata/libgdata-0.17.7.ebuild b/dev-libs/libgdata/libgdata-0.17.7.ebuild
index ce01bdd4863cbf4a101e8430f16edc3849781f11..bf51fdf868fcb4387148f3cc9b43beafd305a572 100644 (file)
--- a/dev-libs/libgdata/libgdata-0.17.7.ebuild
+++ b/dev-libs/libgdata/libgdata-0.17.7.ebuild
@@ -41,8 +41,10 @@ DEPEND="${RDEPEND}
 "
 
 src_prepare() {
-       # https://bugzilla.gnome.org/show_bug.cgi?id=780081
-       eapply -R "${FILESDIR}/${PV}"-streams-https-tests.patch
+       # https://bugzilla.gnome.org/show_bug.cgi?id=780081 - remove with 0.17.8
+       if use test && ! has_version '>=net-libs/libsoup-2.55.90:2.4'; then
+               eapply -R "${FILESDIR}/${PV}"-streams-https-tests.patch
+       fi
        # x86 test fix from upstream git post-0.17.7
        eapply "${FILESDIR}/${PV}"-fix-x86-tests.patch