Richard Levitte - VMS Whacker wrote:
>
> A "make update" may add new symbols to libeay.num and ssleay.num at
> any time. It may as well be symbols that weren't meant to be there
> and that get removed the next day or so... Such changes do not matter
> to the next release, but with the current mkdef.pl, it will take up a
> slot and maybe needlessly so.
>
> I wonder then, would it be a good thing to have the last release
> maximum slot number stored somewhere, to be updated during a release
> only? The purpose of that is that above that number, anything goes,
> functions may be reorganised, removed, readded.
>
> Of course, this means that one snapshot may be icopatible with
> another, and it will require some extra discipline when building a
> release... Which might be done through a Makefile target anyway (no,
> dist isn't quite right).
>
Yes I'd agree with that or at least an option to automate clearing out
the new dev version numbers. Currently such changes will only affect
Windows DLL builds AFAICS.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
