On Thu, Dec 24, 2020 at 6:30 AM Jan Engelhardt
On Thursday 2020-12-24 11:33, İsmail Dönmez wrote:
On 24 Dec 11:28 2020, İsmail Dönmez wrote:
On 24 Dec 11:05 2020, Arjen de Korte wrote:
Could it be I have missed an announcement that Berkeley DB support has to be removed from packages submitted to Factory? Or is there a mailinglist I failed to subscribe to where this was posted?
There is no such rule or discussion. There is some work underway to make it optional which comes from SLE side. So, nothing is being removed.
Btw so far I saw it's being replaced by lmdb, [...]
I like to think of it as "no, not really". A completely unscientific method grepping for BuildRequires shows:
# timespan of about 6½ years Leap 13.2: db 56, lmdb 2, sqlite 66 Leap 42.1: db 54, lmdb 4, sqlite 65 Leap 15.1: db 47, lmdb 7, sqlite 73 Factory today: db 44, lmdb 13, sqlite 79
Which would suggest to me that the replacement is perhaps statistically random with no specific preference for lmdb. And rpm has been vocal about the lmdb shortcomings too.
It was a shame about LMDB because I advocated for it in RPM upstream and shepherded its integration. But LMDB upstream was simply not interested in addressing our concerns after we integrated it. That said, Berkeley DB in openSUSE is old even by most distributions' standards. Unlike everyone else shipping BDB, openSUSE never pulled in BDB 5, and stayed at BDB 4.8. I'm not sure if RPM was the reason why it was held back (which was still not a good reason since RPM itself works with BDB 5 and most distributions were using BDB 5.3 with RPM), but now that it isn't using BDB, if someone cares about BDB in openSUSE, they can upgrade it. Now, insofar as BDB's removal in distributions, Fedora marked BDB as deprecated in Fedora 33[1], switched RPM to use SQLite[2], and is slowly getting the rest of the distribution ported away from BDB. [1]: https://fedoraproject.org/wiki/Changes/Libdb_deprecated [2]: https://fedoraproject.org/wiki/Changes/Sqlite_Rpmdb -- 真実はいつも一つ!/ Always, there's only one truth!