On 18-04-23 17:00:45, James Le Cuirot wrote: > On Mon, 23 Apr 2018 17:47:27 +0200 > Michał Górny <[email protected]> wrote: > > > W dniu pon, 23.04.2018 o godzinie 02∶57 -0500, użytkownik Gordon > > Pettey napisał: > > > On Mon, Apr 23, 2018 at 1:26 AM, Michał Górny <[email protected]> > > > wrote: > > > > W dniu nie, 22.04.2018 o godzinie 09∶34 -0500, użytkownik Matthew > > > > Thode napisał: > > > > > 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. > > > > > > > > > > https://bugs.gentoo.org/653076 has the specifics, but I cannot > > > > > see a reason why we are artifically limiting the backed to just > > > > > one. > > > > > > > > How would you solve the problem of packages requiring specific SSL > > > > backend? Currently they enforce it via USE dependency on cURL. > > > > > > Perhaps with exactly the same USE dependencies that already exists, > > > just without the at-most-one limitation on curl itself? > > > > 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. >
The way that curl installs it's libs for multi-backend (I'm currently using the proposed patch) is to still just install a single library. To get something like debian does with libcurl-gnutls we'd need to do separate builds. -- Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
