From: Allan Hardy
Date: November 9 2005 7:03pm
Subject: RE: License Question
List-Archive: http://lists.mysql.com/plusplus/5124
Message-Id: <1B76D3F17F4BE44283AD3C1C92AB590B0A39AA97@emss04m14.us.lmco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

 
Now wait, if MySQL++ can be dynamically linked to then this is also a
viable option:

	Proprietary app ->
		dynamically linked to LGPL mysql++ ->
		dynamically linked to GPL licensed mysql

Since the LGPL woul isolate the Proprietary App from the GPL copyleft 


Allan


-----Original Message-----
From: Chris Frey [mailto:cdfrey@stripped] 
Sent: Wednesday, November 09, 2005 2:01 PM
To: plusplus@stripped
Subject: Re: License Question

On Wed, Nov 09, 2005 at 11:48:05AM -0700, Warren Young wrote:
> Precisely.  That leads me to:
> 
> 	proprietary app linking to LGPL library: dynamic only
> 
> It is not the only possible way, but it is the only sane way.
> 
> What difficulties remain, once you make that decision?

Only the mysql commercial license.  We now have:

	Proprietary app ->
		dynamically linked to LGPL mysql++ ->
		dynamically linked to commercially licensed mysql

Or:

	Proprietary app ->
		dynamically linked to LGPL mysql++ ->
		dynamically linked to BSD Postgresql

Of course, option 2 is still vapourware. :-)

- Chris


-- 
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:
http://lists.mysql.com/plusplus?unsub=allan.hardy@stripped