Ira Abramov wrote:
Quoting guy keren, from the post of Sun, 25 Feb:
Didn't MySQL used to be plublished under dual licenses? either GPL or
"embedded"?
it still is. however, the other license is commercial - i.e. you need to
pay $$$ for that.
Choo, You've been in this business a long time, I expect more of you...
then read what i write. dispite my confusion, what you quoted me writing
sais "if you want to distribute it under the other license - you need to
pay $$$". i didn't say anything about re-distributing it under the GPL.
technically, thus, i was right, even if i did not understand what i was
trying to say ;)
A dual license means you can choose which license you want to use the
product under. If you choose GPL, it's GPL all the way, you can
redistribute it with source in any way you want along with any product
you want, propriatery or open. dynamicly linking with GPL libraries is
also fine, only static linking isn't.
you're mixing GPL with LPG. you can not link with GPL-ed libraries if
your code's license is not compatible with the GPL. you can link with
LGPL libraries dynamically. actually, you may also link with them
statically, provided that you give the user your object files too, and a
means to re-build the application using a different version of the library.
However, if you want to stick it inside a product (like VersionCue that
is built into all of Adobe's products AFAIK) and you want to patch it,
hide its original name or hard-link it with other code without
redistributing the source, that's when you need to use the other license
(and pay for it), which gives you rights to embed MySQL in your product,
get support for it and so on.
the rest - i agree with.
--guy
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
