future releases of
MySQL > including 4.0.21. However, if 4.0.21 is not out by the
freeze, this
is still a DFSG concern for sarge. If only for the purpose of
raising
awareness of this, this bug should probably remain open as a policy
violation...
As far as I understood Zak Greant (MySQL)
Greetings All,
We have set up a list for discussing MySQL community issues. If anyone
is interested in joining, please send a blank message to
[EMAIL PROTECTED]
The main topic of discussion for the short term will be licensing.
Cheers!
--zak
Greetings Andres,
Thanks for writing.
On Mar 16, 2004, at 01:01, Andres Salomon wrote:
(CC'ing debian-legal for any suggestions they may have, as well)
Excellent!
...
Congrats. Hopefully we'll see v0.2 very soon. :)
We have feedback from many people now to integrate, so there should be
Hi Steve,
On Mar 20, 2004, at 15:42, Steve Langasek wrote:
Hi Zak,
Thanks for your efforts in unravelling this licensing tangle!
Thanks!
One notable omission here is the OpenSSL license, which is similar to
the 4-clause BSD license, but includes additional terms not found in
that license.
On Mar 20, 2004, at 15:42, Steve Langasek wrote:One notable omission
here is the OpenSSL license, which is similar to
the 4-clause BSD license, but includes additional terms not found in
that license.
Ok. Added at
http://zak.greant.com/cvstrac/index.cgi/licensing/tktview?tn=26
Cheers!
--za
5 matches
Mail list logo