Richard Levitte - VMS Whacker wrote:
>
>
> drh> Yes I'd agree with that or at least an option to automate clearing out
> drh> the new dev version numbers. Currently such changes will only affect
> drh> Windows DLL builds AFAICS.
>
> Oh, VMS as well as soon as I've debugged the script I'm working on
> :-).
>
> Now, I'm not entirely sure on exactly what you agree with. If yo read
> carefully, my message has sevaral parts that may be separately
> agreeable :-).
>
OK in more detail...
>
> 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.
>
I agree about storing the last release slot number somewhere maybe in
the .num files themselves?
Wwrt this "reorganisation": provided it doesn't mean that adding or
deleting a single function could potentially result in a large portion
of the .num file being reordered on the next "make update" then that's
OK by me.
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]
