Hi,
El 15/12/10 14:15, Marcus Rueckert escribió:
On 2010-12-15 18:02:17 +0100, andreas.hanke@gmx-topmail.de wrote:
or add cryptopp-5.6.1 to factory with the Debian SONAME (since there are so many distibution-invented SONAMES already that we don't to need to invent our own, and Fedora's one is broken) and update python-cryptopp to make it use the external cryptopp package.
this solution imho.
Yep, I would pick that one too.
I have done part of this locally (created a libcryptopp package based on the one in devel:libraries:c_c++, updated to version 5.6.1, built as a shared library with ".so.9"), all with plain rpmbuild. How can I get involved to get this submitted? The next step would be to update python-cryptopp in factory to make use of it, i.e. --disable-embedded-cryptopp. (The build currently fails for an unrelated reason; maybe 0.5.12 is too old for Python 2.7?) Andreas -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org