Hi Wei,
This will probably be a sore subject for some...
As an Administrator, it disgusts me that '<someprog> --version' does
not correctly report its version and revision, or does not report that
the base package has been modified (or tampered). A concrete example
of the problem in another package: its damn near impossible to tell
what version of OpenSSL (0.9.8 {k|l|m|n|o}) is running on a given
Linux distribution because of grafting, back-porting, and the
Frankenstein-ian patch work.
Though I don't understand why someone would not use the latest stable
version of Crypto++ from SVN, I don't take offense to using all
revisions up to and including the revision of interest.
Would you consider adding a license term to the effect? Your license
is pretty unrestricted, and the Open Source community seems to be
willing to put up with minor inconveniences: the OpenSSL license
requires a narcissistic shout-out for the original authors (who are no
longer part of the project).
Jeff
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
