| 1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
| 2 |
Hash: SHA256
|
| 3 |
|
| 4 |
On Thu, 27 May 2021 00:41:23 +0200
|
| 5 |
David Seifert <soap@g.o> wrote:
|
| 6 |
|
| 7 |
> The old Berkeley DB slots need to go at this point. The Base Project has |
| 8 |
> decided to consider BDB a deprecated database backend, and we'll slowly |
| 9 |
> be working towards a (possibly) BDB-free ::gentoo some time in the long- |
| 10 |
> term future. |
| 11 |
|
| 12 |
I think we should keep at least one non AGPLv3 berkdb in the tree as long
|
| 13 |
as we have any packages that unconditionally depend on it. June 1st is
|
| 14 |
too short a time frame for masking pre AGPLv3 berkdb versions. I think it
|
| 15 |
is reasonable to fix packages that either force berkdb USE flags on in their
|
| 16 |
deps, or have a hard dep (either by updating/fixing or last-rite).
|
| 17 |
|
| 18 |
|
| 19 |
> Other distros such as Fedora have started a gradual phase-out of |
| 20 |
> Berkeley DB too, given Oracle's strong-armed approach to community |
| 21 |
> input and their arguably hostile switch to the AGPLv3 |
| 22 |
> (https://fedoraproject.org/wiki/Changes/Libdb_deprecated). Furthermore, |
| 23 |
> Oracle is known to remove critical features from BDB in patch releases, |
| 24 |
> such as the removal of the client-server architecture and the SQL API |
| 25 |
> between 18.1.32 and 18.1.40. |
| 26 |
|
| 27 |
Gradual phase-out is also the approach we should take. Dropping non
|
| 28 |
AGPLv3 version sort of immediately forces the issue for users that
|
| 29 |
can't or won't accept that license.
|
| 30 |
|
| 31 |
> To this end, we will also be removing USE="berkdb" from |
| 32 |
> profiles/default/linux/make.defaults. If you implicitly depend on |
| 33 |
> profiles enabling optional use of sys-libs/db, you will need to enable |
| 34 |
> this USE flag yourself, beginning 1st June. |
| 35 |
> |
| 36 |
> From here on, you should be working under the assumption that the |
| 37 |
> sys-libs/db package will be gone from the Gentoo repository within |
| 38 |
> **two years** from the time of this news item. If you depend on BDB in |
| 39 |
> a production environment, we strongly suggest you move to one of the |
| 40 |
> modern replacements, such as GDBM, SQLite or LMDB. |
| 41 |
|
| 42 |
This makes sense for end users, but we should fix ::gentoo before we
|
| 43 |
force it on our users.
|
| 44 |
-----BEGIN PGP SIGNATURE-----
|
| 45 |
|
| 46 |
iQIzBAEBCAAdFiEE4/aZebtLiSjaeOPRfL9E71w1CIMFAmCu1TgACgkQfL9E71w1
|
| 47 |
CIMU4A//RRAogOgwFcjLpDy3Xb5oJLVBfdO5XOhaYsVi8omafDS5lMdS2MlXE1t1
|
| 48 |
F6t3Q69yJ3vTxd7wVArnhEQCAqNpjUgRu8wFmmWQTy8hj5qOhLJEdirY1m6RqS//
|
| 49 |
BNjPYTPfPUsPyR112QZSxQ0X5YzoWJWHM2IBQ3ccDaVskHPpQTUPnfIJ72p4v69H
|
| 50 |
fNZQMDEPI9SsIL3iZtjFl9E00/FHZy24VXDyQqOAuIeE34V6Bt2Ph1Zw9ZxPlZCM
|
| 51 |
iybwOVMIfR3eAPIz6HZK1ImyFo6srBjyky1lOVQ5fgGi/vMDrID4YH6effD71DUM
|
| 52 |
mZkxLPYl78Pyzd20fK2ca0udc7HgEVqyoCcgpVzdpVzHpwwaVGWYl8HL1FCJlING
|
| 53 |
hgO4eMMbSaMVK8dMUvA/uUt1oLJVYXSFjPBGtg16lPjLCOY6UZsv6L5Lxs/tbqJa
|
| 54 |
GU0rRMuUJ2FqnJebcNfT80st1ZS+x14xy6Xg6e20+NKXMMzmBlnWZyDn5Z5ZBFAK
|
| 55 |
aHE4llH2a9lNSAis8z7sW0mm92Zy65LhZrtYbmhPtfoXlwHOzGdev/5ifTjnFhl4
|
| 56 |
w70XzeRtHHZTzCbBHTPO+e/14lVV8zG5LNCc1+FYeD73XCDxrnBP/8Eavns0/zf7
|
| 57 |
IHyCWJQ5T4y6gr4Gpjmo3urhzTBX9sR4arFYefSshGiNB/hRgfE=
|
| 58 |
=3x1D
|
| 59 |
-----END PGP SIGNATURE----- |
Archives