#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 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?
Adding such a field will wrongly encourage client libraries/programs to do
different things with cryptopp based on the variant string. If there are
reasons why client libraries/programs would access cryptopp in different
ways, they should test for different cases on a feature-by-feature basis
instead of on a fragile variant string.
If different variants of cryptopp are installed by distros in ways that
differe so much that this version extension is deemed necessary, then the
cryptopp project should look at why its buildsystem is not meeting the
needs of packagers.
@zooko: You don't need the CRYPTOPP_EXTRA_VERSION support in your
ubuntu/debian packages because pycrypto doesn't break when
CRYPTOPP_EXTRA_VERSION is undefined.
--
Ticket URL: <http://sourceforge.net/apps/trac/cryptopp/ticket/11#comment:3>
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.
