On 12 Feb 2004, Greg Stark wrote:
>
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
>
> > Now, if you don't mind using the ODBC connector, you're scott free. but
> > you WILL be bound by the GPL, and the GPL (not MySQL's interpretation,
> > just the GPL in general) being applied to connect libs
So are you saying that if you connect to any GPL database (e.g. gnumed
is a GPL database created with Postgresql), you must GPL your code? Even
when using something like ODBC as the connection method?
I don't think so. The difference is, that PostgreSQL is BSD and you are
connecting from a GPL
SCO is acting on advice from attorneys as well.
My last post.;^)
>>> Richard Welty <[EMAIL PROTECTED]> 02/17/04 05:38PM >>>
On Wed, 18 Feb 2004 00:30:58 - Greg Sabino Mullane <[EMAIL PROTECTED]> wrote:
attribution of my quote of Theo de Raadt got stripped some how:
> >"Free means free"
>
On Tue, 10 Feb 2004 15:32:11 -0500 Chris Browne <[EMAIL PROTECTED]> wrote:
> There's certainly room for PostgreSQL to have a sub-motto something
> like:
> _PostgreSQL: Free software means no need to fear license audits._
here's something that Theo de Raadt says (in the context of OpenBSD)
that
John DeSoi wrote:
Scott,
On Feb 10, 2004, at 2:06 PM, scott.marlowe wrote:
Now, if you don't mind using the ODBC connector, you're scott free.
but
you WILL be bound by the GPL, and the GPL (not MySQL's interpretation,
just the GPL in general) being applied to connect libs seriously limits
your
[EMAIL PROTECTED] ("scott.marlowe") wrote:
> no kidding. I have to admit that in my mad scientist moments, I have
> envisioned writing a new connect lib that's BSD/LPGL licensed. Primarily
> just because I can be a bit antisocial... :)
A group of users, distressed at license changes, proposed
On Tue, 10 Feb 2004, Andrew Sullivan wrote:
> On Tue, Feb 10, 2004 at 12:06:43PM -0700, scott.marlowe wrote:
> > simple. They GPL'd their connection libs. So, if you write code that has
> > their connection libs in it, it's gotta be GPL'd.
>
> Yes. But you could fork from their old libs (whic
On Tue, 10 Feb 2004, Andrew Sullivan wrote:
> On Tue, Feb 10, 2004 at 09:50:31AM -0700, scott.marlowe wrote:
> > you would still be wholly bound by the GPL. I.e. all the code you write
> > that connects to MySQL would therefore have to be GPL'd. I.e. it does
> > nothing to fix the licensing pr
On Tue, Feb 10, 2004 at 12:06:43PM -0700, scott.marlowe wrote:
> simple. They GPL'd their connection libs. So, if you write code that has
> their connection libs in it, it's gotta be GPL'd.
Yes. But you could fork from their old libs (which were, IIRC, LGPL)
and work from there. Of course, yo
On Tue, Feb 10, 2004 at 09:50:31AM -0700, scott.marlowe wrote:
> you would still be wholly bound by the GPL. I.e. all the code you write
> that connects to MySQL would therefore have to be GPL'd. I.e. it does
> nothing to fix the licensing problems that have been brought up.
I know that's what
10 matches
Mail list logo
