Re: Licensing issues including another projects source code into the jdbc driver

From: "Dave Cramer" <dave(at)fastcrypt(dot)com>
To: "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>
Cc: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Licensing issues including another projects source code into the jdbc driver
Date: 2001-11-05 19:59:43
Message-ID: 00af01c16634$6957d160$8201a8c0@inspiron
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Umm ok,

This is dissappointing; kind of defeats the purpose of being able to
leverage open source code for the good of all open source projects. It
isn't that big a deal, we can write our own logging package.

Dave

-----Original Message-----
From: Peter Eisentraut [mailto:peter_e(at)gmx(dot)net]
Sent: November 5, 2001 3:05 PM
To: Dave Cramer
Cc: 'Bruce Momjian'; pgsql-hackers(at)postgresql(dot)org
Subject: RE: [HACKERS] Licensing issues including another projects
source code into the jdbc driver

Dave Cramer writes:

> I presume you are referring to the 3rd clause? What is the issue with
> this clause?

It would require everyone that ships a product based on the JDBC driver
to
mention this acknowledgement in advertisements, which is annoying and
impractical. More generally, it would introduce a divergence in
licensing
in PostgreSQL, which should be avoided.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2001-11-05 20:00:39 Re: compiler warnings in ODBC
Previous Message Tom Lane 2001-11-05 19:20:04 Re: Proposal: 7.2b2 today