1 |
On Fri, 30 Oct 2015 18:25:14 -0400 |
2 |
Rich Freeman <rich0@g.o> wrote: |
3 |
|
4 |
> On Fri, Oct 30, 2015 at 5:16 PM, Anthony G. Basile <blueness@g.o> wrote: |
5 |
> > On 10/30/15 3:35 PM, hasufell wrote: |
6 |
> >> |
7 |
> >> On 10/30/2015 06:55 PM, Michał Górny wrote: |
8 |
> >>> |
9 |
> >>> We have no way of saying 'I prefer polarssl, then gnutls, then |
10 |
> >>> libressl, and never openssl'. |
11 |
> >> |
12 |
> >> I don't think this is something that can be reasonably supported and it |
13 |
> >> sounds awfully automagic. And I don't see how this is possible right |
14 |
> >> now, so I'm not really sure what you expect to get worse. |
15 |
> >> |
16 |
> >> E.g. -gnutls pulling in dev-libs/openssl is not really something you'd |
17 |
> >> expect. If we go for provider USE flags, then things become consistent, |
18 |
> >> explicit and unambiguous. The only problem is our crappy implementation |
19 |
> >> of providers USE flags via REQUIRED_USE. |
20 |
> >> |
21 |
> > I'm not sure what mgorny has in mind, but the problem I see with saying I |
22 |
> > want just X to be my provider system wide is that some pkgs build with X |
23 |
> > others don't, other pkgs might need a different provider. So it might make |
24 |
> > sense to order them in terms of preference: X1 > X2 > X3 ... and then when |
25 |
> > emerging a package, the first provider in the preference list that works is |
26 |
> > pulled in for that package. |
27 |
> |
28 |
> I think that would be useful in general. It would probably not be |
29 |
> useful in this case, since it was somebody's bright idea to make it |
30 |
> essentially impossible to install two of the options on the same |
31 |
> system (and that wasn't directed at hasufell). Users could of course |
32 |
> still express the preference, but the PM would need to be smart enough |
33 |
> to ignore that preference on 95% of packages that support both options |
34 |
> so that it can take the lower preference on the 5% of packages that |
35 |
> only support the option the user didn't really want. |
36 |
|
37 |
No, that's not *the* problem. LibreSSL vs OpenSSL is actually |
38 |
the *least* problematic one since we intend to support them as |
39 |
'drop-in-plus-rebuild' replacements. |
40 |
|
41 |
The real problem is those fancy upstreams who believe they're doing |
42 |
everyone a favor by providing the choice between multiple SSL |
43 |
providers. This is what brings the real conflicts here, and this what |
44 |
often loves to break stuff even further by introducing cross-package |
45 |
implementation match requirements... |
46 |
|
47 |
-- |
48 |
Best regards, |
49 |
Michał Górny |
50 |
<http://dev.gentoo.org/~mgorny/> |