MySQL client libraries licensing (was Fedora Core 2 wishlists)

Adam Debus rhl at reachone.com
Thu Dec 11 00:21:10 UTC 2003


Yeah, I had that explained to me a couple times through private e-mail so
far today.

I think I shant be using said lawyer again for this sort of work. :)

Thanks,

Adam Debus
Network Engineer, ReachONE Internet
adam at reachone.com

----- Original Message ----- 
From: "Alan Cox" <alan at redhat.com>
To: <fedora-devel-list at redhat.com>
Sent: Wednesday, December 10, 2003 4:10 PM
Subject: Re: MySQL client libraries licensing (was Fedora Core 2 wishlists)


> On Wed, Dec 10, 2003 at 10:57:11AM -0800, Adam Debus wrote:
> >     As it has been explined to me by a lawyer: That's only true if you
are
> > embedding the mysql library in your software (statically linking).
Merely
> > using MySQL as a database for PHP does not tie you to either license
because
> > you are not embedding code from either program.
>
> You are embedding the client library and a derivative work of it. The core
> dbase has always been GPL which isnt a problem, now the client libraries
> are
>
> >     The same goes for Perl or C/C++. Writing code that utilizes the
language
> > does not automatically tie you to the license the programming language
uses,
> > unless you statically link against the libraries.
>
> If you call functions provided by the interpreter ...
>
> >     Otherwise, pretty much nothing in Linux would be other then GPL,
since
> > that's what glibc is licensed under, including PHP, Perl and Apache, all
of
> > which have licenses other then GPL.
>
> glibc has specific statements to cover linking for apps. Guess why
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-devel-list
>





More information about the fedora-devel-list mailing list