| 1 |
On Tuesday 15 December 2009 03:05:33 Peter Volkov wrote: |
| 2 |
> Hi. How do we choose USE flags in case package supports different ssl |
| 3 |
> implementations? |
| 4 |
> |
| 5 |
> Currently we do this differently: 1. some packages use ssl USE flag and |
| 6 |
> additional gnutls (or openssl) to select alternative ssl implementation, |
| 7 |
> 2. other packages already started to avoid ssl USE flag completely and |
| 8 |
> use only openssl/gnutls/nss. |
| 9 |
> |
| 10 |
> The latter makes things harder for those who want ssl enabled packages |
| 11 |
> on the system and don't care about implementation. Also it is not |
| 12 |
> intuitive to have packages without ssl with ssl USE flag enabled system |
| 13 |
> wide. So I would like to ban latter solution and suggest the following: |
| 14 |
> |
| 15 |
> |
| 16 |
> If package has ssl support use ssl USE flag for that. In case there are |
| 17 |
> alternatives, use openssl/gnutls/nss for upstream _less_ recommended |
| 18 |
> implementation(s). |
| 19 |
|
| 20 |
USE=ssl should select *some* implementation. the finer grained |
| 21 |
openssl/gnutls/nss can be used to select a specific implementation, but not |
| 22 |
respecting USE=ssl is broken. curl is an example of this. |
| 23 |
-mike |
Archives