To push any license violations on to the user instead of the
distributor?
Cute. Why not just add an exception to your license?
I am afraid you got me wrong here. I did not use the term "compatible"
to mean license compatibility. I wanted to know whether an application
which dlopens libssl.so.0.9.8 could safely use libssl.so.0.9.8b
instead, without causing any API/ABI breakage?
Sorry for the misunderstanding.
Thanks,
Debarshi
--
GPG key ID: 63D4A5A7
Key server:
pgp.mit.edu