| 1 |
On 10/28/2015 09:36 AM, Alexis Ballier wrote: |
| 2 |
> On Wed, 28 Oct 2015 03:06:59 +0100 |
| 3 |
> hasufell <hasufell@g.o> wrote: |
| 4 |
>> A is not that difficult. Most uses of 'openssl' can just be replaced |
| 5 |
>> with 'ssl', others probably with '!gnutls?' even. A few exotic ones |
| 6 |
>> might stay and we will have to advice users to set USE="openssl |
| 7 |
>> libressl" instead of USE="-openssl libressl". |
| 8 |
>> B will definitely be more work, but ofc is also a lot cleaner and |
| 9 |
>> totally unambigous. |
| 10 |
> |
| 11 |
> |
| 12 |
> You haven't taken into consideration the licence incompatibilities: |
| 13 |
> http://www.gnu.org/licenses/license-list.en.html#OpenSSL |
| 14 |
> it gets really messy for libraries: a gpl binary linking against a |
| 15 |
> library linking against openssl means the binary can be |
| 16 |
> redistributed, but not with such a library linked against openssl... |
| 17 |
> |
| 18 |
> the point of the 'openssl' useflag is to have something that is not |
| 19 |
> enabled by default and that can be used in RESTRICT="openssl? |
| 20 |
> ( bindist )" expressions... |
| 21 |
> |
| 22 |
|
| 23 |
|
| 24 |
You can just do RESTRICT="ssl? ( bindist )" and disable bindist by |
| 25 |
default or vote for solution B. |
Archives