From:
[email protected]
Hi,
Robert Millan:
Please use gcrypt11 instead. Programs still using gcrypt1 should be updated.
Is the API different, or only ABI? If it's only ABI, I don't mind asking maintainers to change the build dependency. Otherwise I really don't have time to help on this.
It's a different API. The changes are pretty simple to do, though;
the most invasive is to replace
STRUCT *fn_returning_struct(...)
with
ERRCODE fn_returning_struct(...,&STRUCTPTR)
Post-Sarge, gcrypt1 will disappear from Debian, so there's no way around
doing it in one way or another. Ideally, it's Upstream's job since those library versions are *old*, unmaintained, they can't talk to all modern
secure servers, and they have memory leaks.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de |
[email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBHdC18+hUANcKr/kRAv13AJ4yOJzZYg41yNNNkq1FrwBddAk6gQCglzZd NDPTrh80vOX88uUQQpKxC6s=
=Nan+
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)