Re: cvs commit: openssl/apps Makefile.ssl

[Richard Levitte - VMS Whacker]

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).

-- 
Richard Levitte   \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]