On Mar 14, 2005, at 1:02 PM, David R. Morrison wrote:
Lars,
Thanks for raising this issue. It has come up before, but it has perhaps
not received the attention it deserves.
My reading of the links you provided suggests that you are correct: we may
not link GPL'd software against fink's openssl package unless the license
explictly permits linking to openssl. (In many cases, there is an
alternative -- link to the system's openssl -- although this is not great
because it doesn't get updated as frequently.)
Do we do this in stable/crypto at all? Did you happen to jot down the names of the offending packages in unstable/crypto?
It would be a long list! Some examples that I found are xchat-ssl, wget-ssl, valknut-ssl, sylpheed-ssl, stunnel4, squid-ssl, socat-ssl, and sitecopy-ssl. I assume the same packages in stable would also be affected if indeed this is a problem. I realize licensing issue are a headache, and I am sorry for bringing this up, I just would like to do the right thing. ...so would linking against the system's libssl be ok as far as fink's policies are concerned?
Thanks, Dave
To: fink-devel@lists.sourceforge.net From: Lars Rosengreen <[EMAIL PROTECTED]> Subject: [Fink-devel] the gpl and openssl Date: Mon, 14 Mar 2005 12:32:09 -0800
I would like to figure out if it is ok for me to create a gpl'd package that links against fink's libssl. Looking in unstable/crypto, it looks like there are several packages that do this, yet I have read elsewhere that doing so violates the gpl because openssl's license is not compatible with the gpl. The gpl has an exemption for libraries that are distributed with the operating system, but I'm not sure if that would also cover fink's openssl package. Some enlightenment would be much appreciated :)
http://www.gnome.org/~markmc/openssl-and-the-gpl.html http://www.fsf.org/licensing/licenses/gpl-faq.html#GPLIncompatibleLibs http://www.openssl.org/support/faq.html#LEGAL2
thanks, -Lars
-- Lars Rosengreen <[EMAIL PROTECTED]> http://www.margay.org/~lars
smime.p7s
Description: S/MIME cryptographic signature