| 1 |
Anthony G. Basile posted on Thu, 29 May 2014 13:42:01 -0400 as excerpted: |
| 2 |
|
| 3 |
> With the number of ssl providers growing, like libressl, and with issues |
| 4 |
> like bug #510974, I think its time we consider making this a uniform way |
| 5 |
> of dealing with ssl providers in gentoo. We would proceed something |
| 6 |
> like this: |
| 7 |
> |
| 8 |
> 1. Introduce a new USE_EXPAND called SSL which mirrors CURL_SSL --- |
| 9 |
> becuase CURL_SSL is too provincial a name. |
| 10 |
> |
| 11 |
> 2. migrate curl and all its dependencies to the SSL use expand. |
| 12 |
> |
| 13 |
> 3. Migrate over all consumers of ssl to the new SSL use expand system. |
| 14 |
> |
| 15 |
> What do people think? |
| 16 |
|
| 17 |
What about an ssl.eclass to handle it? |
| 18 |
|
| 19 |
Obviously Peter's concern about packages that only support some of the |
| 20 |
options would need to be taken into account, with some sort of variable, |
| 21 |
say SSL_SUPPORTED, that would be set before eclass inheritance. Then the |
| 22 |
eclass could formalize the general dependency logic and expose variables |
| 23 |
of its own that could in turn be used to set package specific options. |
| 24 |
|
| 25 |
Or is package handling too individualized for an eclass to work well, |
| 26 |
even with a mechanism to tell the eclass which ssl providers were |
| 27 |
supported and further mechanisms to allow package specific logic where |
| 28 |
required? |
| 29 |
|
| 30 |
-- |
| 31 |
Duncan - List replies preferred. No HTML msgs. |
| 32 |
"Every nonfree program has a lord, a master -- |
| 33 |
and if you use the program, he is your master." Richard Stallman |
Archives