Hi Paul
On 04/09/2009, at 7:10 PM, Paul McCullagh wrote:
Thanks for giving us the inside on that one. It has been a point of
confusion for me, and I have read the GPL a few times to try to
figure it out.
Oh look the GPL and its FAQ sorts out most, and my article on the
dev.mysql.com site
Hi Arjen,
Thanks for giving us the inside on that one. It has been a point of
confusion for me, and I have read the GPL a few times to try to figure
it out.
In the meantime I am certain that my understanding is correct, that
there is nothing illegal about shipping mysqld with a closed sou
On Sep 4, 2009, at 2:20 AM, Arjen Lentz wrote:
Hi Mark
On 04/09/2009, at 9:25 AM, MARK CALLAGHAN wrote:
Back in the day there was an assertion in the MySQL internals PDF
with
respect to the license of any client library created after reading
that doc. The PDF has been replaced by HTML and I
Hi Mark
On 04/09/2009, at 9:25 AM, MARK CALLAGHAN wrote:
Back in the day there was an assertion in the MySQL internals PDF with
respect to the license of any client library created after reading
that doc. The PDF has been replaced by HTML and I don't see that claim
anymore. Does anyone remember
On Thu, Sep 3, 2009 at 4:09 PM, Arjen Lentz wrote:
> Hi Paul
>
> On 03/09/2009, at 10:54 PM, Paul McCullagh wrote:
>>
>> As far as I know, with the advent of the BSD licensed libdrizzle
>> (https://launchpad.net/libdrizzle), which also runs with MySQL (and I assume
>> MariaDB), the dual licensing m
Hi Paul
On 03/09/2009, at 10:54 PM, Paul McCullagh wrote:
As far as I know, with the advent of the BSD licensed libdrizzle (https://launchpad.net/libdrizzle
), which also runs with MySQL (and I assume MariaDB), the dual
licensing model is now irrelevant.
You're legally correct (apart from li
6 matches
Mail list logo
