On 12/05/11 12:55 AM, Jayashankar K B wrote:
Does that mean, we have to distribute whole source code including our
proprietary software source?
Nope. PostgreSQL is released under a BSD-like license that imposes very
few requirements. It's short and easy to read, so the best thing to do
is go read it. The short version is that BSD-licensed code is used all
over the place in closed-source apps where it's embedded entirely into
the app, so you're not going to have problems just using libpq and
postgresql in an embedded app.
If you're using PostGIS, that might be different as the PostGIS
extensions are GPL licensed. See the PostGIS website for information on
that; I don't know enough to comment further.
On 12/05/2011 04:59 PM, John R Pierce wrote:
you're using Linux, which is GPL. you need to *CAREFULLY* read the
GPL and go over this with your lawyers. have fun. I'm not a lawyer,
nor do I play one on TV.
This isn't really the place for a Linux/BSD flamewar, nor a licensing
debate re the Linux kernel. The OP should use the existing extensive
resources about Linux licensing in embedded systems. In terms of what
must be released, have a look at what Linksys (now Cisco) are releasing
- it's their kernel and any (L)GPL userspace components, but not their
own stuff.
Note that relying on a full-GPL library that you directly link to
clearly *does* require you to license your own code under the GPL.
Anything short of that is grades of fuzzy.
--
Craig Ringer
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
