--On Monday, March 23, 2015 11:49 PM +0000 Ken Moffat
<[email protected]> wrote:
LMDB also does not have any releases so far, only a git tree.
http://symas.com/mdb/ - apparently postfix supports it, and there
are patches for e.g. Cyrus-SASL, but most BLFS packages are not
mentioned.
This is incorrect. LMDB has had many releases, and many projects support
LMDB or have patches to add support:
<http://symas.com/mdb/#projects>
quanah@zre-ldap001:~/src/openldap/mdb.0.9/libraries/liblmdb$ grep Release
CHANGES
LMDB 0.9.15 Release Engineering
LMDB 0.9.14 Release (2014/09/20)
LMDB 0.9.13 Release (2014/06/18)
LMDB 0.9.12 Release (2014/06/13)
LMDB 0.9.11 Release (2014/01/15)
LMDB 0.9.10 Release (2013/11/12)
LMDB 0.9.9 Release (2013/10/24)
LMDB 0.9.8 Release (2013/09/09)
LMDB 0.9.7 Release (2013/08/17)
LMDB 0.9.6 Release (2013/02/25)
LMDB 0.9.5 Release (2012/11/30)
Regardless, what we're talking about here strictly at the moment is
OpenLDAP, which bundles LMDB and does not need (nor should it be used with)
a separate LMDB library.
Strong words. Anybody who has registered for the wiki can update the
instructions. Some of what is there is good, other comments are old or
maybe even wrong.
Many things are well documented, but not necessarily common
knowledge. We do not usually need to get involved in license
policing.
<http://lwn.net/Articles/557820/>
But that includes: Russ Allbery also commented that AGPL was not
written for libraries, and as a result has terms that are difficult
to interpret for non-web-applications.
In other words, it is unclear how it applies.
It is the opinion of the OpenLDAP project that the AGPL is not compatible
with OpenLDAP's license, and linking to BDB 6.x puts users in jeopardy of a
legal shakedown from Oracle. This is really quite well documented in the
infoworld article:
"To work with the new license, Berkeley DB users will need to make sure
their whole Web app is compliant with the AGPL. First, they now need to
make full corresponding source to their Web application available. Second,
they need to ensure the full app -- previously considered an internal-use
asset -- has compatible and compliant licensing. That means the whole
source has to be licensed under the GPLv3 or the AGPL, as well as made
available to all users."
OpenLDAP is not licensed under the GPLv3 OR AGPL. Thus it already fails
the compliance test. Given that LDAP is a network protocol, it (like web
applications), has "remote clients", which triggers the AGPL compliance
requirements.
I do see that fedora and debian are both using v5 - fedora's git
tree is at http://pkgs.fedoraproject.org/cgit/libdb.git/tree/
Sure, there's nothing wrong with BDB v5's license. It is only 6.x and
later BDB where the license was changed.
Perhaps we should put a NOTE in the berkeleydb page, pointing out
that this verion is licensed under the Affero GPL v3 which might
have implications for those who run programs on a server and let
other users communicate with it there -
https://www.gnu.org/licenses/why-affero-gpl.html
There is no reason for the BDB documentation to exist on the page at all.
The wiki should not mention BDB at all, and remove all the patch notes, and
instead correctly instruct people to build OpenLDAP with the included LMDB
backend.
For openldap, most of the docs (e.g. in their wiki) that google
found talk about using berkeleydb (without, AFAICS, mentioning that
it needs to be an old version, so I really don't see the problem ?
Wikipedia thinks you are an active openldap contributor, so please
spell out in detail what the problem would be if I were to link an
openldap server to db v6.
Already answered above.
Note that I have no interest in building an openldap server, to me
the openldap client is just another of those awkward "required to
be able to build something else, even if not used" packages.
The OpenLDAP client libraries don't link to BDB or LMDB, so the client
libraries are immaterial. This issue purely relates to the OpenLDAP server
code, which is where BDB would be used.
--Quanah
--
Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
