Re: [ossig] CA open-sources Ingres database - News & Technology -CNETAsia

[Dinesh Nair <dinesh@xxxxxxxxxxxx>]

On Thu, 27 May 2004, Kenneth Wong wrote:

> We're arguing about two different things. Note below:

i see where you're coming from. see comments below:

> Once again, I'm talking about the GPL mysql. Once released under the
> GPL, that version of mysql is governed by the GPL rules and ONLY the GPL
> rules, since GPL is very intolerant of other rules.

exactly. so, even if you're basing your app off the GPL version of MySQL,
and your app was closed source, you'd not be able to do that as then your
app would be violating the GPL. so, you're thus

1. forced to release your app under the GPL, or
2. pay mysql to link against the commercially licensed version.

> > <quote>
> > If you distribute a proprietary application in any way, and you are
> > not licensing and distributing your source code under GPL, you need
> > to purchase a commercial license of MySQL
> > </quote>
>
> GPL has no such requirement. Sorry, but you released your version of
> mysql into the wild as the GPL. It's now only bound by the GPL.

but it does, the very viral nature of it will infect your app the moment
you link in the mysql libraries which are GPLed. the only way to bypass
the "source distribution" is to link your app against the commercial
licensed version of mysql which does not have the "must distribute source
with binaries" requirement.

so, mysql are in fact using the viral nature of the gpl to force people
who use their engines/libraries to GPL their apps. if they choose not to,
mysql provides them an option to purchase a copy of mysql engine/libraries
under a non-GPL license.

> If mysql is GPL and they closely link with GPL libraries, then your
> entire code is GPL. This is not their requirement, it's the GPL's

but it is their requirement. they're saying that if you're using their GPL
version, then your app must be GPL/OSS as well.

(granted, we playing semantics here. the GPL is the one which mandates
this specifically, but mysql has chosen the GPL and has that same intent
as well)

> Sorry, but if I follow the rules of the GPL, then I can use #1 WITHOUT a
> separate license from MySQL. Their own darned fault for releasing under

yes you absolutely can. but then by doing that, your apps have to be GPLed
too, which is something the GPL enforces.

> Despite all this, I do believe that it's probably best to license from
> MySQL where possible. However, I'm arguing that MySQL corporation's
> interpretation of the GPL is flawed, largely by their profit goals.

me too. it's the spirit of things which i am more concerned with, and the
spirit of what they do is palatable to me.

Regards,                           /\_/\   "All dogs go to heaven."
dinesh@alphaque.com                (0 0)    http://www.alphaque.com/
+==========================----oOO--(_)--OOo----==========================+
| for a in past present future; do                                        |
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo "The opinions here in no way reflect the opinions of my $a $b."  |
| done; done                                                              |
+=========================================================================+


---------------------------------------------------------
To unsubscribe: send mail to ossig-request@mncc.com.my
with "unsubscribe ossig" in the body of the message