In article <[EMAIL PROTECTED]> you wrote:
> "Ralf S. Engelschall" <[EMAIL PROTECTED]>:
>
>> Yes, Ben is right: At the release level people can use OPENSSL_VERSION_NUMBER
>> and that should be enough. When we start at the development level to increase
>> a number for every API change we get the same chaos as for Apache: it's often
>> forgotten, people complain about two much such numbers to check for, etc. pp.
>
> We *could* add a file with an extra #define that is automatically set
> to the current date each time a snapshot is tar'ed -- e.g.
>
> #define OPENSSL_VERSION_DATE 0x19990518
Yes, an automatic and simple approach like this is ok.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
