On May 24, 2008, at 1:07 PM, Ralf S. Engelschall wrote:

> On Sat, May 24, 2008, Jeff Johnson wrote:
>
>> Nothing wrong with this change, but likely needs to be done as
>> a macro persistently at run-time so that the --usecrypto
>> doesn't have to be explictly added to each invocation when multiple
>> implementations are present.
>
> Yes, the macro is still on my list. The question is just where the  
> best
> code location is to expand a "%_usecrypto" macro?
>

Usually I just oneshot expand a macro where needed. The need is
on 1st call through pgpImplVec ...

Verifying the macro values as you have just added to --usecrypto is  
trickier,
perhaps time to teach rpmExpand() about expliitly enumerated strings.

>> And dlopen() eventually to Have it yer own way! AutoFu
>> choice is restrictive: if not compiled in, well, that crypto
>> implementation is unavailable. Period.
>
> dlopen() is not such easy. You also have to dlsym() all
> necessary symbols, etc.

Yep. Luckily only one symbol in all of rpm{bc,nss,ssl,gc}.c,
and only a couple of symbols in rpmio/lzdio.c (can likely
be reduced to a single symbol).

73 de Jeff