#11: include a field for a distribution- or variant- specific version number
------------------------+---------------------------------------------------
Reporter: zooko | Owner:
Type: enhancement | Status: new
Priority: major | Version:
Keywords: |
------------------------+---------------------------------------------------
Comment(by zooko):
Replying to [comment:3 ohnobinki]:
> Why should cryptopp clients need to know what variant of cryptopp is
being talked to? Regardless of whether or not a variant is being talked
to, the API/ABI/semantics should stay the same, shouldn't they?
Like Jeffrey mentioned, this is mostly for humans to inspect. It can be
useful to know the difference between "Crypto++ v6.0 with the first two
Debian patches" vs. "Crypto++ v6.0 with one pycryptopp patch" vs.
"Crypto++ v6.0 compiled from pristine upstream source".
--
Ticket URL: <http://sourceforge.net/apps/trac/cryptopp/ticket/11#comment:4>
cryptopp <http://sourceforge.net/projects/cryptopp/>
SF-project cryptopp
--
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.
