| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 10/28/2015 12:23 PM, Anthony G. Basile wrote: |
| 5 |
> On 10/28/15 7:16 AM, hasufell wrote: |
| 6 |
>> On 10/28/2015 07:23 AM, Ryan Hill wrote: |
| 7 |
>>> Agreed. If there's one choice then "ssl" should be used. |
| 8 |
>>> openssl/libressl/etc should really be considered sub-flags of |
| 9 |
>>> ssl. |
| 10 |
> |
| 11 |
> This is what I did with curl. USE=ssl means one and exactly one |
| 12 |
> ssl provider must be specified. I suggested making it a model |
| 13 |
> gentoo wide, but there were criticisms, I forget what, but the made |
| 14 |
> sense to me at teh time. |
| 15 |
|
| 16 |
Such a setup makes sense to me as well, although likely want it to be |
| 17 |
more generic and maybe use a prioritized list rather than a use expand |
| 18 |
per package / group of packages. Maybe something similar to |
| 19 |
python_compat can be used for the TLS / crypto provider |
| 20 |
|
| 21 |
|
| 22 |
- -- |
| 23 |
Kristian Fiskerstrand |
| 24 |
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net |
| 25 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
|
| 28 |
iQEcBAEBCgAGBQJWMLIvAAoJECULev7WN52Fdb8IALLlM/763gnsx3iEc7NIh7IL |
| 29 |
HWDfBwfY2vuDKWGGVlKIXn2CZfIrDhcqOZxtprFcrK073q+Gu6ZDqVd+og+EWTJw |
| 30 |
Erv7aq5Mi4poBPtcQT6P3CJG77RXCQPdzgPG6K8FaWyVPh+RkKFr7VsJ615visk6 |
| 31 |
UmRbwpehU51Vb/qTWl94J1z0SvIo3gusSzeK9FpkSFimrZQtsByWFtIijWYeToLH |
| 32 |
Mv4hl7BVwpHWctTwLDObuqkl+zWEITapJ3CIYz93jrfnyWZXi/DFvOyWcK3YOES2 |
| 33 |
vDcIDWGKt0SunZgka0VTJ+CTbfCcuvxb0sXUJfJNdy6P/p7aJyzZllPEZ2ciVVk= |
| 34 |
=iN64 |
| 35 |
-----END PGP SIGNATURE----- |
Archives