| 1 |
Dear all, |
| 2 |
|
| 3 |
I'm a bit late to the party, but here is my $0.02: |
| 4 |
|
| 5 |
> REQUIRED_USE=" |
| 6 |
> curl_ssl_winssl? ( elibc_Winnt ) |
| 7 |
> ssl? ( |
| 8 |
> ^^ ( |
| 9 |
> [...] |
| 10 |
> ) |
| 11 |
> )" |
| 12 |
|
| 13 |
I don't like this. If the user specifies several SSL providers in |
| 14 |
make.conf, it should mean that any of these is fine and the ebuild can |
| 15 |
choose an arbitrary one. The exactly-one-of operator would cause emerge |
| 16 |
to complain in this case and possibly force the user to have complex |
| 17 |
package.use setups. |
| 18 |
|
| 19 |
> With the number of ssl providers growing, like libressl, and with |
| 20 |
> issues like bug #510974, I think its time we consider making this a |
| 21 |
> uniform way of dealing with ssl providers in gentoo. We would proceed |
| 22 |
> something like this: |
| 23 |
> |
| 24 |
> 1. Introduce a new USE_EXPAND called SSL which mirrors CURL_SSL --- |
| 25 |
> becuase CURL_SSL is too provincial a name. |
| 26 |
> |
| 27 |
> 2. migrate curl and all its dependencies to the SSL use expand. |
| 28 |
> |
| 29 |
> 3. Migrate over all consumers of ssl to the new SSL use expand system. |
| 30 |
> |
| 31 |
> What do people think? |
| 32 |
|
| 33 |
I think a better name for the USE_EXPAND would be CRYPTO_PROVIDER (or |
| 34 |
similar) instead of just SSL, as the libraries are not strictly used for |
| 35 |
SSL but also for other forms of crypto (e.g. [1]). |
| 36 |
|
| 37 |
|
| 38 |
Best regards, |
| 39 |
Chí-Thanh Christopher Nguyễn |
| 40 |
|
| 41 |
|
| 42 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=512664 |
Archives