From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Shachar Shemesh <psql(at)shemesh(dot)biz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: License question |
Date: | 2004-04-22 16:56:46 |
Message-ID: | 200404221856.46322.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Shachar Shemesh wrote:
> Can anyone shed more light on this point for me? Am I misreading
> something? If it is possible to put code into an LGPL project, what
> is the requirement?
You have to display the PostgreSQL license text in the source code or
the binary, depending on what you ship. A strict interpretation would
say that considering the combined work, this is an additional
requirement on top of the [L]GPL, so it is not allowed by the terms of
the [L]GPL. (But it is allowed by the terms of the PostgreSQL
license.) A looser interpretation would say that what the PostgreSQL
license text says is essentially a subset of what the [L]GPL already
says anyway, so adding the requirements of the PostgreSQL license on
top of it does not actually impose additional requirements, so there is
no problem. Which one of these interpretations you believe is between
you and the copyright holders of that LGPL'ed work, but the PostgreSQL
copyright holders don't care.
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql | 2004-04-22 17:00:04 | Re: contrib vs. gborg/pgfoundry for replication solutions |
Previous Message | Min Xu (Hsu) | 2004-04-22 16:50:50 | Re: valgrind errors |