PostODBC...
Hi...
I got ahold of Julie today (maintainer of PostODBC) about including the
PostODBC stuff as part of the general distribution, so that we pretty much
had all the interfaces covered.
Julie agreed, and uploaded a zip file of the current sources for me to
integrate into the source tree...which I did...and then *very* quickly
undid...PostODBC falls under LGPL, and therefore can't be included as part of
our source distribution without contaminating our code :(
Does anyone know of *any* way around this? Like, can a section of our
distribution contain software that falls under LGPL without it affecting *our*
copyright (Berkeley)? Or does it have to remain completely seperate? Its
effectively a seperate package, but because its wrapped in our "tar" file
for distribution, how does that affect things?
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
The Hermit Hacker wrote:
Hi...
I got ahold of Julie today (maintainer of PostODBC) about including the
PostODBC stuff as part of the general distribution, so that we pretty much
had all the interfaces covered.Julie agreed, and uploaded a zip file of the current sources for me to
integrate into the source tree...which I did...and then *very* quickly
undid...PostODBC falls under LGPL, and therefore can't be included as part of
our source distribution without contaminating our code :(Does anyone know of *any* way around this? Like, can a section of our
distribution contain software that falls under LGPL without it affecting *our*
copyright (Berkeley)? Or does it have to remain completely seperate? Its
effectively a seperate package, but because its wrapped in our "tar" file
for distribution, how does that affect things?
I'm no expert, but (for example) RedHat distributes Linux as well as commercial
products on the same CDROM. There are separate licensing statements for each
category of software. It would seem to be the same issue with us; we aren't
_forcing_ someone to use both categories...
- Tom
On Wed, 7 Jan 1998, Thomas G. Lockhart wrote:
I'm no expert, but (for example) RedHat distributes Linux as well as commercial
products on the same CDROM. There are separate licensing statements for each
category of software. It would seem to be the same issue with us; we aren't
_forcing_ someone to use both categories...
Right, this I have no problems with...but, would that mean that we could
distribute it as PostODBC.tar.gz on the same CD as PostgreSQL-v6.3.tar.gz, or
as part of the overall tar file? Where does the line get drawn? :(
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
Julie agreed, and uploaded a zip file of the current sources for me to
integrate into the source tree...which I did...and then *very* quickly
undid...PostODBC falls under LGPL, and therefore can't be included as part of
our source distribution without contaminating our code :(Does anyone know of *any* way around this? Like, can a section of our
distribution contain software that falls under LGPL without it affecting *our*
copyright (Berkeley)? Or does it have to remain completely seperate? Its
effectively a seperate package, but because its wrapped in our "tar" file
for distribution, how does that affect things?Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
By LGPL, I assume you mean the library version of GPL. I thought that the whole
point of the library version was that it didn't contaminate any other code.
That's how commercial products can release executables which are linked with
the GNU libc (or whatever) without the whole product falling under the GPL.
Andrew
----------------------------------------------------------------------------
Dr. Andrew C.R. Martin University College London
EMAIL: (Work) martin@biochem.ucl.ac.uk (Home) andrew@stagleys.demon.co.uk
URL: http://www.biochem.ucl.ac.uk/~martin
Tel: (Work) +44(0)171 419 3890 (Home) +44(0)1372 275775
Import Notes
Resolved by subject fallback