I wrote:
> Pretty much, but you must provide your software in a form that can be
> relinked.
Karen Hill writes:
> What does that mean?
What it says: read the LGPL. If you are dynamically linking you need do
nothing special as you are already providing your code in linkable form.
You also need no
John Hasler wrote:
> > Npgsql is LGPL. It means you must release the source of Npgsql when
> > distributing it, and if you modify Npgsql, but not have to release the
> > source under the (L)GPL of the software that calls Npgsql functions?
>
> Pretty much, but you must provide your software in a
Karen Hill writes:
> If you make create a PostgreSQL database that uses PostGIS and you
> distribute that database, than your database (tables, stored procedures,
> views, etc) are GPL?
No.
> Like wise if you create a client that connects to that database, do they
> also become GPL?
No.
> Does
Merijn de Weerd wrote:
[...]
> If you distribute the PostgreSQL server software linked with
> the PostGIS software, then you have to comply with the GPL
> for both parts of that derivative work.
>
> If you don't distribute any server software, you do not have
> to worry about what the GPL require
On 2006-10-20, Karen Hill <[EMAIL PROTECTED]> wrote:
> If you make create a PostgreSQL database that uses PostGIS and you
> distribute that database, than your database (tables, stored
> procedures, views, etc) are GPL?
No, because those tables, stored procedures etc. are not
derivative works of
I was looking through the various contrib packages and pgfoundry
projects. I noticed that many of them are GPL like PostGIS or LGPL
like Npgsql. I have questions.
If you make create a PostgreSQL database that uses PostGIS and you
distribute that database, than your database (tables, stored
proc
