MySQL licensing and OpenSSL linking issues
Hello
Attached and below you'll find the recent plans of MySQL regarding
their licenses. I would think that this is sufficient for the
Debian project. If not please scream loud now! :-)
bye,
-christian- / mysql maintainer
> Date: Thu, 5 Jun 2003 17:42:42 -0600
> From: Zak Greant <zak@mysql.com>
> To: ch@debian.org
> Cc: David Axmark <david@mysql.com>
>
> Dear Christian,
>
> Sorry for the long delay on this matter!
>
> Here is our initial plan to fix the problems that been created by the
> change in licensing.
>
> We are considering offering a blanket exception that will allow MySQL to
> be used in combined works where the combined work is licensed under one
> or more OSI approved licenses.
>
> This will allow most (if not all) free and open source software projects
> to continue to use MySQL as they always have and will ensure that
> combined works created using GPL-licensed MySQL must still release
> their source and allow others to copy, modify and distribute it.
>
> Additionally, it helps ensure that closed source applications that
> require MySQL software must use the commercial MySQL license if the
> combined work is to be distributed.
>
> Of course, we would like feedback from the community on this issue,
> rather than making an arbitrary change and encountering more problems.
> :)
>
> So, will this change meet the needs of the Debian community?
>
> Can you see problems with this approach?
>
>
> Cheers!
> --zak
------------------------
> Of course, a few minutes after I sent my last message, I forgot to
> mention that we would have a specific exception for OpenSSL.
>
> Bleh. I hate licensing issues. :)
>
> --zak
Reply to: