This might be relevant for bsddb-6.0.0, which doesn't show this message but has the same license: Found Berkeley DB 6.0 installation. include files in /usr/include library files in /usr/lib64 library name is libdb-6.0 Detected Berkeley DB version 6.0 from db.h ******* COMPILATION ABORTED ******* You are linking a Berkeley DB version licensed under AGPL3 or have a commercial license. AGPL3 is a strong copyleft license and derivative works must be equivalently licensed. You have two choices: 1. If your code is AGPL3 or you have a commercial Berkeley DB license from Oracle, please, define the environment variable 'YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION' to any value, and try to install this python library again. 2. In any other case, you have to link to a previous version of Berkeley DB. Remove Berlekey DB version 6.0 and let this python library try to locate an older version of the Berkeley DB library in your system. Alternatively, you can define the environment variable 'BERKELEYDB_DIR', or 'BERKELEYDB_INCDIR' and 'BERKELEYDB_LIBDIR', with the path of the Berkeley DB you want to use and try to install this python library again. Sorry for the inconvenience. I am trying to protect you. More details: https://forums.oracle.com/message/11184885 http://lists.debian.org/debian-legal/2013/07/ ******* COMPILATION ABORTED ******* * ERROR: dev-python/bsddb3-6.0.1::gentoo failed (compile phase): * (no error message)
From ChangeLog: "6.0.1: ... * If you want to link with Oracle Berkeley DB 6.0, you will need to create the environment variable 'YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION' to signal to the pybsddb that you are legal. To be legal, your code MUST be AGPL3 *OR* you have to buy a commercial license from Oracle. If you are not legally entitled to use Berkeley DB 6.0 and you have previous versions of Berkeley DB on your system, you can a) delete Berkeley DB 6.0 and try again, OR b) instruct pybsddb to use a previous Berkeley DB version, using environment variables or command line options." Licenses team: Should ebuild set YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION environmental variable?
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #1) > * If you want to link with Oracle Berkeley DB 6.0, you will > need to create the environment variable > 'YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION' > to signal to the pybsddb that you are legal. To be legal, > your code MUST be AGPL3 *OR* you have to buy a commercial > license from Oracle. IMHO this is just nonsense. Both AGPL-3 and BSD are approved as Free Software licenses by both the FSF and the OSI, and the (3-clause) BSD license is GPL-compatible. It should be no problem to link such code together and distribute the resulting binary (under the terms of both BSD and AGPL-3, of course). Even DB itself contains some code that is BSD licensed. Disclaimer: IANAL, TINLA.
*bsddb3-6.1.0 (27 Jul 2014) 27 Jul 2014; Ian Delaney <idella4@gentoo.org> +bsddb3-6.1.0.ebuild: bump; drop py2.6, upgrade test phase
Before somebody re-closes this bug behind my back again: The build failure stated in comment 0 still occurs with sys-lib/db:6.0 and bsddb3-6.1.0. The WORKSFORME resolution was due to lack of proper testing, not any sort of fix.
Is it possible to get a second opinion from the licenses team on this? I certainly appreciate ulm's feedback, but I want to be a bit more sure on this before we intentionally circumvent a check put in place by the upstream developer.
Created attachment 382142 [details, diff] Add agplv3 use flag to optionally use db-6.x Here's a sort of hacky solution: We can utilize a use flag in LICENSE and depend on appropriate version of DB. This way, people who don't want to accept AGPLv3 for their projects can bypass it and we will build against an older DB version.
+ 03 Aug 2014; Mike Gilbert <floppym@gentoo.org> bsddb3-6.1.0.ebuild: + Introduce bindist use flag to control dependency on db-6.x. Bug 494490.
(In reply to Mike Gilbert from comment #7) > + 03 Aug 2014; Mike Gilbert <floppym@gentoo.org> bsddb3-6.1.0.ebuild: > + Introduce bindist use flag to control dependency on db-6.x. Bug 494490. Reopening. There is no licensing conflict to start with, therefore the bindist flag is unnecessary. See comment #2.
(In reply to Ulrich Müller from comment #8) > Reopening. There is no licensing conflict to start with, therefore the > bindist flag is unnecessary. See comment #2. This compromise was reached after discussion with robbat2 in #gentoo-dev.
I will leave this open until the license team can reach some agreement.
+ 03 Aug 2014; Mike Gilbert <floppym@gentoo.org> bsddb3-6.1.0.ebuild: + Drop bindist use flag; BSD and AGPLv3 are compatible.
