1 |
On Thu, 2020-12-31 at 02:50 +0000, Peter Stuge wrote: |
2 |
> Michał Górny wrote: |
3 |
> > > > I think the three main ways forward from here would be to |
4 |
> > > > either: |
5 |
> > > > |
6 |
> > > > 1. Keep LibreSSL for indefinite time (possibly masked) |
7 |
> > > > 2. Eventually move LibreSSL to libressl overlay. |
8 |
> > > > 3. Eventually remove LibreSSL. |
9 |
> > > |
10 |
> > > 4. A libressl or libressl-libtls ebuild installs only libtls. |
11 |
> > |
12 |
> > dev-libs/libretls already does that. |
13 |
> |
14 |
> dev-libs/libretls doesn't install a libressl libtls. |
15 |
> |
16 |
> This thread is obviously about how the libressl implementation remains |
17 |
> in use. |
18 |
> |
19 |
> It's clear now that you want to hinder that in Gentoo at any cost to |
20 |
> the community, but that's not useful, so please take a step back |
21 |
> unless |
22 |
> you are actually going to be constructive. |
23 |
> |
24 |
> My proposition 4. (which I suggested already earlier - you shouldn't |
25 |
> have ignored it) is obviously not about having any libtls provider in |
26 |
> the tree, but to model reality accurately and ensure that libretls is |
27 |
> the primary and prefered libtls provider, since it is literally the |
28 |
> libtls upstream. |
29 |
> |
30 |
> It is important to me that you can choose dev-libs/libretls instead of |
31 |
> having any libretls code on your systems, but I reject you forcing |
32 |
> that |
33 |
> choice of yours on everyone else. |
34 |
> |
35 |
> |
36 |
> //Peter |
37 |
> |
38 |
|
39 |
Patches welcome. |