On 12/02/2013 07:50 PM, Paul Eggert wrote: > On 12/02/2013 06:12 AM, Pádraig Brady wrote: >> To use this from coreutils I configure with --with-openssl >> and add in the appropriate libs as follows. >> Note since the new libs are required, then is one of the reasons >> I didn't enable this by default. A related question though >> is I'd like coreutils to change the default to enable this by default. >> What would be the best way to do that, while still allowing users >> to --with-openssl=no > > Thanks for doing all this work! Sorry, I don't understand what > you mean by "the new libs are required". Won't the code still > work even if libcrypto is absent, just as it did before?
It will work as before if libcrypto is absent. If however libcrypto is present then there will be new references to the libcrypto routines and each project would have to add LIB_CRYPTO_MD5 etc. to their list of libs similarly to the coreutils patch I had inline in my previous mail. > I would think that this change should be enabled by default. > I'd want it enabled for Emacs, for example. If some app > doesn't want it enabled by default we can worry about that > then. If the above change in link requirements isn't too onerous to push to gnulib users, then I also think it should be enabled by default. I'd add an entry to NEWS of course indicating the change. thanks, Pádraig.
