Hi all involved, On Sun, 2006-12-03 at 01:03 -0600, Peter Samuelson wrote: > Sorry for the dupe, Adam beat me to this one. No problem. To tell the truth, I knew something is coming.
> See #401398 for my > proposed solution, which is basically to put the following in both > shlibs files: > libneon 26 libneon26 | libneon26-gnutls I don't know software patents and so, but I think the meaning that a software can not link to OpenSSL directly or indirectly means runtime linking also disallowed. Also this would be true only if the library names would differ. But both packages have the same library name, libneon.so.26.0.2 . So IMHO the solution would be to change libneon26-gnutls to provide libneon-gnutls.so.26.0.2 What's the release team point Vorlon? Thanks, Laszlo/GCS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
