Re: cvs commit: openssl/apps Makefile.ssl

[Richard Levitte - VMS Whacker]

From: Dr S N Henson <[EMAIL PROTECTED]>

drh> I agree about storing the last release slot number somewhere maybe in
drh> the .num files themselves?

I was pondering that.  Perhaps as a "special" symbol, starting with
some odd character like...  '&'?  I dunno, it does complicate the
parser as well as the writer a bit.  I think I'd prefer to go for the
KISS principle and have it in separate files, libeay.max and
ssleay.max perhaps?

drh> Wwrt this "reorganisation": provided it doesn't mean that adding or
drh> deleting a single function could potentially result in a large portion
drh> of the .num file being reordered on the next "make update" then that's
drh> OK by me.

I'd say that we can have mkdef.pl take another argument, say
"release", where it will simply cut libeay.num and ssleay.num after
the last release max slot number and reinsert all functions that are
above it, unless they have disappeared.  Is that good enough not to
make you jump up and down in frustration?  :-)

-- 
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]