You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by James Mansion <ja...@mansionfamily.plus.com> on 2009/08/01 09:05:48 UTC
Re: [jira] Created: (QPID-2017) Files for Async Store interface layer
(NOTE, read carefully - license issues)
Kim van der Riet (JIRA) wrote:
> They are encumbered with BDB, which is used to save the broker state. For this reason, these files are LGPL
Why are they encumbered with BDB? You aren't redistributing BDB are you?
And even if you deem that referencing symbols in BDB is somehow
'redistribution' of
(part of) BDB, why does that make it LGPL?
Surely it just requires:
'Redistributions in any form must be accompanied by information on
how to obtain complete source code for the DB software and any
accompanying software that uses the DB software.'
(And that 's more like GPL, than LGPL)
I'm not sure how referencing BDB symbols can be redistributing BDB,
but I guess Sleepycat and Oracle have no interest in clarity on that.
The symbols are discussed in books and documentation and used from code
that could be considered as the source of snippets used. APR has code that
can use BDB doesn't it?
James
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [jira] Created: (QPID-2017) Files for Async Store interface layer
(NOTE, read carefully - license issues)
Posted by James Mansion <ja...@mansionfamily.plus.com>.
Kim van der Riet wrote:
> IANAL, you may be correct. However, this decision was made about 2 years
> ago out of an abundance of caution regarding non-apache-compatible
> licenses. The reason LGPL was selected was that it is suited for use
> with libraries (which this is - msgstore.so) which can be run against
> the apache-licensed qpidd.
>
OK, so its self-inflicted. Shame its not dual-licensed as Apache/LGPL
with a tear-off option.
Or BSD.
Its just that it seemed to me similar to the APRutil/BDB situation - my
recollection was that the
BDB interface code was retained in-tree but that it was not compiled by
default in case a user
infected their own code.
It probably is better that it evolves into an interface implementation
anyway - hopefully Windows
will pick up a Jet implementation. Presumably you could ship a SQLite
one as a refeernce.
(Some things, COM did get right - we've been rather hasty as an industry
to abandon it, just
because of the registry - which is actually not a direct requirement anyway)
Thanks
James
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [jira] Created: (QPID-2017) Files for Async Store interface
layer (NOTE, read carefully - license issues)
Posted by Kim van der Riet <ki...@redhat.com>.
On Sat, 2009-08-01 at 08:05 +0100, James Mansion wrote:
> Kim van der Riet (JIRA) wrote:
> > They are encumbered with BDB, which is used to save the broker state. For this reason, these files are LGPL
> Why are they encumbered with BDB? You aren't redistributing BDB are you?
No.
> And even if you deem that referencing symbols in BDB is somehow
> 'redistribution' of
> (part of) BDB, why does that make it LGPL?
>
> Surely it just requires:
>
> 'Redistributions in any form must be accompanied by information on
> how to obtain complete source code for the DB software and any
> accompanying software that uses the DB software.'
>
> (And that 's more like GPL, than LGPL)
IANAL, you may be correct. However, this decision was made about 2 years
ago out of an abundance of caution regarding non-apache-compatible
licenses. The reason LGPL was selected was that it is suited for use
with libraries (which this is - msgstore.so) which can be run against
the apache-licensed qpidd.
> I'm not sure how referencing BDB symbols can be redistributing BDB,
> but I guess Sleepycat and Oracle have no interest in clarity on that.
>
> The symbols are discussed in books and documentation and used from code
> that could be considered as the source of snippets used. APR has code that
> can use BDB doesn't it?
>
> James
Whatever the reasons, the bottom line is that this interface code is
currently LGPL, and the process outlined in this JIRA is the one
suggested by Apache legal to get it into the current Qpid source tree.
Kim
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org