>special case. It'll have to be pretty severe to justify breaking the entire
>existing code base.
How about keeping symlinks in place for a transition period? Then old
applications can be built unmodified, but if a name conflict occurs
the user can simply rm -f include/*.h
After some time (perhaps when other API changes become necessary), we
can remove those links.
Oh, and I vote for naming the next release 1.0. When someone switches
to the openssl/*.h includes, they can simply tell their users they
need at least OpenSSL 1.0. Makes more sense than 0.9.3. :)
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
