The following applies if you DISTRIBUTE and only IF,
In house or internal use has no obligations legally what so ever. You
are not obligated to provide the changes back to the MySQL++ team, not
legally though morally you have consider your self.
Also, note you can static link all day, as long as its internal use.
There is none of the other happy crap about derived works to be
concerned with.
But for distribution:
LGPL and GPL require you to either provide source or make an offer for
source. You are much better off providing source at the same time as
you provide executables.
An offer, such as email me, go to my web site, etc, must be available
for 3 years and must be available to the public. Hence you get into the
distribution business. If you ship source at the same time as the
executables, then your done, no further obligations to provide the
source to anyone else.
The above applies to the source for MySQL++ and any changes you have
made.
Lastly, you cannot point people to the MySQL++ site as a way to meet
your obligation to provide source for MySQL++
This is because of the 3 year requirement. Unless you have cut a deal
with someone else, such as the MySQL team, that they promise to make the
source (for that version) available for 3 years, then you have to meet
that obligation yourself. You can't simply point to someone else.
Hope that helps.
Allan
-----Original Message-----
From: Mark Merendino [mailto:Mark.Merendino@stripped]
Sent: Wednesday, November 09, 2005 4:15 PM
To: Hardy, Allan; MySQL++ Mailing List
Subject: RE: License Question
All this talk of Licenses has lead me to a question of my own. Feel
free not to respond if you all are fed up with the license talk
If I am working on an a propriotery application and Im using a version
of MySQL++ that I have made modifications to, what are my
responsibilities?
Im gathering from earlier discussion that I can not link staticly. So I
guess I need to link dynamically. But do I also need to distribute the
mysql++ source along with the modifications I have made?
-----Original Message-----
From: Hardy, Allan [mailto:allan.hardy@stripped]
Sent: Wednesday, November 09, 2005 4:01 PM
To: MySQL++ Mailing List
Subject: RE: License Question
>>Ah, no. The most restrictive license always obtains.
Ok, now I will argue :) 0r respectively disagree, but I guess there is
limited reason to continue I will just state where I am at.
I do not see the path that allows GPL to reach through the LGPL code and
affect the proprietary application?
We have gLib Applications that are not licensed as GPL (they use various
open/semiopen licenses).
It seems to me as if this all creates an unhealthy scenario that would
allow me to get around having to use commercial MySQL.
Not sure if they will respond but sent an email to licensing at the FSF
asking about the Prop->LGPL->GPL scenario
Actually I am not clear on how a derived work of an GPL product can be
licensed under LGPL?
I asked them about that as well.
(I didn't ask them directly but since MySQL++ was originally calling
LGPL MySQL, now that MySQL has changed to GPL, doesn't MySQL++ need to)
I'll leave you all alone as this is taken you into debian land :) but I
do appreciate the thought provoking and educational input.
If I get any response from FSF I will update you all if interested
Allan
-----Original Message-----
From: Warren Young [mailto:mysqlpp@stripped]
Sent: Wednesday, November 09, 2005 2:53 PM
To: MySQL++ Mailing List
Subject: Re: License Question
Hardy, Allan wrote:
>
> 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
Ah, no. The most restrictive license always obtains.
If your statement were the case, then on Linux, the LGPL nature of glibc
would free a lot of apps from needing to be GPL.
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus To unsubscribe:
http://lists.mysql.com/plusplus?unsub=1
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus To unsubscribe:
http://lists.mysql.com/plusplus?unsub=1
SPECIAL NOTICE
All information transmitted hereby is intended only for the use of the
addressee(s) named above and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution of
confidential and privileged information is prohibited. If the reader of
this message is not the intended recipient(s) or the employee or agent
responsible for delivering the message to the intended recipient, you
are hereby notified that you must not read this transmission and that
disclosure, copying, printing, distribution or use of any of the
information contained in or attached to this transmission is STRICTLY
PROHIBITED.
Anyone who receives confidential and privileged information in error
should notify us immediately by telephone and mail the original message
to us at the above address and destroy all copies. To the extent any
portion of this communication contains public information, no such
restrictions apply to that information. (gate02)

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.