[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: MySQL-OpenSSL linking, news by MySQL team.about licensing

On Wed, Apr 02, 2003 at 06:03:18PM +0200, Andreas Metzler wrote:
> On Wed, Apr 02, 2003 at 09:54:41AM -0600, Steve Langasek wrote:
> > On Wed, Apr 02, 2003 at 01:26:35PM +0200, Francesco P. Lovergine wrote:
> >> we have some news about #167747 which is potentially of interest
> >> of all packages which links OpenSSL libraries and MySQL libraries.

> >> MySQL libraries currently are plain GPL, NOT LGPL as someone thought.

> > Unless they're trying to retroactively revoke the LGPL license, versions
> > of the libs prior to MySQL 4.0 are still available under thh LGPL.
> [...]

> It's not that simple.

> Quoting myself in http://bugs.debian.org/168554
> |Nevertheless this does not make libmysqlclient10 licensed under LGPL
> |because mysql-dfsg-3.23.53/libmysql/net.c includes mysqld_error.h, a
> |GPLed file.
> |
> |Please clarify this issue with upstream, whether this was an accident
> |and libmysqlclient10 is supposed to be LGPL or if it was intended and
> |libmysqlclient10 is indeed licensed under GPL.
>           cu andreas

Looking at the contents of mysqld_error.h on my system, I would assert
that nothing within it is copyrightable, at least in the US.  It is
nothing more than a list of defines mapping textual error code names to
their numeric values.  If someone believes this is really a licensing
concern, you can eliminate the dependency easily enough by grepping the
LGPL sources for references to 'ER_*', and empirically determining their
values either by consulting documentation or looking at the wire.  But
again, I assert that because this would produce an almost verbatim copy
of the existing file, doing so would be nothing more than superfluous

Steve Langasek
postmodern programmer

Attachment: pgp28UOruRjZ4.pgp
Description: PGP signature

Reply to: