Re: Humor me: Postgresql vs. MySql (esp. licensing) - Mailing list pgsql-general

From scott.marlowe
Subject Re: Humor me: Postgresql vs. MySql (esp. licensing)
Date
Msg-id Pine.LNX.4.33.0310100935160.19056-100000@css120.ihs.com
Whole thread Raw
In response to Re: Humor me: Postgresql vs. MySql (esp. licensing)  (Martin Marques <martin@bugs.unl.edu.ar>)
List pgsql-general
On Fri, 10 Oct 2003, Martin Marques wrote:

> El Jue 09 Oct 2003 22:44, Marsh Ray escribió:
> > Just out of curiosity, what does Debian make MySQL's rather bizarre
> > interpretaion of the GPL:
> >
> > http://www.mysql.com/documentation/mysql/bychapter/manual_Introduction.html
> >#Copyright --- begin quote ----
> >
> > You need a commercial license:
> > [...]
> >     When you distribute a non-|GPL| application that *only* works with
> > the |MySQL| software and ship it with the |MySQL| software. This type of
> > solution is considered to be linking even if it's done over a network.
> >
> > --- end quote ----
> > "Linking over a network"? What stops some GPL'ed web server (or
> > commercial one for that matter) from demanding non-free licensing for
> > web clients that connect to it?
>
> I would like to know what Debian is going to do with PHP and MySQL. There's
> alot of talk about this in the PHP related lists.
> PHP folks do think that there may be some sort of incompatibility between the
> two licenses.

Basically, if you include MySQL connect libs in PHP and distribute it PHP
now falls under the GPL.  Since PHP's license expressly forbids
relicensing, they are incompatible to distribute together.  This was
caused by MySQL changing their connect libs from LGPL to GPL.  It's why
PHP now no longer includes MySQL connect libs in their source tree.


pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: Humor me: Postgresql vs. MySql (esp. licensing)
Next
From: "Thomas LeBlanc"
Date:
Subject: Execute Function from VB/ADO