1 |
On Mon, 23 Apr 2018 17:47:27 +0200 |
2 |
Michał Górny <mgorny@g.o> wrote: |
3 |
|
4 |
> W dniu pon, 23.04.2018 o godzinie 02∶57 -0500, użytkownik Gordon |
5 |
> Pettey napisał: |
6 |
> > On Mon, Apr 23, 2018 at 1:26 AM, Michał Górny <mgorny@g.o> |
7 |
> > wrote: |
8 |
> > > W dniu nie, 22.04.2018 o godzinie 09∶34 -0500, użytkownik Matthew |
9 |
> > > Thode napisał: |
10 |
> > > > The short of it is that curl supports having multiple |
11 |
> > > > backends. I'd like to have that feature enabled so libraries |
12 |
> > > > and userland can choose the backend they wish to use. |
13 |
> > > > |
14 |
> > > > https://bugs.gentoo.org/653076 has the specifics, but I cannot |
15 |
> > > > see a reason why we are artifically limiting the backed to just |
16 |
> > > > one. |
17 |
> > > |
18 |
> > > How would you solve the problem of packages requiring specific SSL |
19 |
> > > backend? Currently they enforce it via USE dependency on cURL. |
20 |
> > |
21 |
> > Perhaps with exactly the same USE dependencies that already exists, |
22 |
> > just without the at-most-one limitation on curl itself? |
23 |
> |
24 |
> This doesn't guarantee that the required backend will actually be |
25 |
> used. Well, unless it blocks any other USE flag from being enabled |
26 |
> but that defeats the purpose. |
27 |
|
28 |
Proprietary software that's linked against a specific backend usually |
29 |
links to libcurl-gnutls.so.4 or whatever specifically as that's what |
30 |
Debian provides. If it points to just libcurl.so.4 but only works |
31 |
against a specific backend then we could use chrpath to change it to |
32 |
the specific name. |
33 |
|
34 |
-- |
35 |
James Le Cuirot (chewi) |
36 |
Gentoo Linux Developer |