Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] About GPL and proprietary software

From: elein <elein(at)varlena(dot)com>
To: Kaarel <kaarel(at)future(dot)ee>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-advocacy(at)postgresql(dot)org,doug(at)mcnaught(dot)org
Subject: Re: [GENERAL] About GPL and proprietary software
Date: 2003-08-31 18:54:23
Message-ID: 20030831115423.D8513@cookie (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-general
Cross-posted to pgsql-advocacy in response to Doug's
comment that:
>This is neither a GNU nor a MySQL mailing list.  I suggest you take
>your question to one of those places, as you'll get a better answer.

Responses to pgsql-advocacy... I hate cross-posting, too.

The information is pertinent to postgreSQL because our
BSD license is a "selling point" for us.  We need to know the differences
between BSD and other licensing schemes.

--elein


On Sun, Aug 31, 2003 at 03:26:24PM +0300, Kaarel wrote:
> I don't feel very confident when it comes to software licenses. But 
> there are some cases I would like to make myself clear. What I am 
> particulary interested in is when does GPL license become restrictive? 
> For example say a company has a proprietary software product that only 
> works with MySQL and no other database system. Are the following cases 
> legal?
> 1) This company sells his product under proprietary license and leaves 
> it up to the client to set up required MySQL server. Or perhaps helps 
> the client with seting up MySQL with or without extra fee.
> 2) Clients pay monthly fee to this company for using their proprietary 
> software which uses MySQL hosted in the companys server.
> 3) This company sells his product under proprietary license on the CD 
> which also includes MySQL as free bonus (with source code).
> 
> If these cases are valid, then when does GPL license for MySQL (or any 
> other software in that matter) become truly restrictive for a 
> proprietary company?
> 
> Kaarel
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>      joining column's datatypes do not match

In response to

pgsql-advocacy by date

Next:From: Ron JohnsonDate: 2003-08-31 19:26:14
Subject: Re: About GPL and proprietary software
Previous:From: Ian BarwickDate: 2003-08-31 18:47:15
Subject: The "Why Postgres not MySQL" bullet list

pgsql-general by date

Next:From: Ron JohnsonDate: 2003-08-31 19:26:14
Subject: Re: About GPL and proprietary software
Previous:From: Doug McNaughtDate: 2003-08-31 18:38:24
Subject: Re: About GPL and proprietary software

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group