From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B44F21382C5 for ; Mon, 23 Apr 2018 16:00:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 052B0E0BC5; Mon, 23 Apr 2018 16:00:55 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AECC9E0BBC for ; Mon, 23 Apr 2018 16:00:54 +0000 (UTC) Received: from red.yakaraplc.local (host213-123-185-55.in-addr.btopenworld.com [213.123.185.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: chewi) by smtp.gentoo.org (Postfix) with ESMTPSA id 05683335C36 for ; Mon, 23 Apr 2018 16:00:52 +0000 (UTC) Date: Mon, 23 Apr 2018 17:00:45 +0100 From: James Le Cuirot To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] multi-backend support for ssl/tls in curl Message-ID: <20180423170045.39edb652@red.yakaraplc.local> In-Reply-To: <1524498447.1791.0.camel@gentoo.org> References: <20180422143402.kemnvlhshhu5x2pr@gentoo.org> <1524464794.1361.9.camel@gentoo.org> <1524498447.1791.0.camel@gentoo.org> X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 62b3a543-ce8b-4895-95c7-304add640d9e X-Archives-Hash: 98aff750b641aed023b1064b0dc2d70e On Mon, 23 Apr 2018 17:47:27 +0200 Micha=C5=82 G=C3=B3rny wrote: > W dniu pon, 23.04.2018 o godzinie 02=E2=88=B657=E2=80=89-0500, u=C5=BCytk= ownik Gordon > Pettey napisa=C5=82: > > On Mon, Apr 23, 2018 at 1:26 AM, Micha=C5=82 G=C3=B3rny > > wrote: =20 > > > W dniu nie, 22.04.2018 o godzinie 09=E2=88=B634=E2=80=89-0500, u=C5= =BCytkownik Matthew > > > Thode napisa=C5=82: =20 > > > > The short of it is that curl supports having multiple > > > > backends. I'd like to have that feature enabled so libraries > > > > and userland can choose the backend they wish to use. > > > >=20 > > > > https://bugs.gentoo.org/653076 has the specifics, but I cannot > > > > see a reason why we are artifically limiting the backed to just > > > > one.=20 > > >=20 > > > How would you solve the problem of packages requiring specific SSL > > > backend? Currently they enforce it via USE dependency on cURL. =20 > >=20 > > Perhaps with exactly the same USE dependencies that already exists, > > just without the at-most-one limitation on curl itself?=20 >=20 > This doesn't guarantee that the required backend will actually be > used. Well, unless it blocks any other USE flag from being enabled > but that defeats the purpose. Proprietary software that's linked against a specific backend usually links to libcurl-gnutls.so.4 or whatever specifically as that's what Debian provides. If it points to just libcurl.so.4 but only works against a specific backend then we could use chrpath to change it to the specific name. --=20 James Le Cuirot (chewi) Gentoo Linux Developer