Mailinglist Archive: opensuse-factory (355 mails)

< Previous Next >
Re: [opensuse-factory] Tumbleweed - Review of the weeks 2020/11 & 12
On Fri, Mar 20, 2020 at 12:01 PM Stephan Kulow <coolo@xxxxxxx> wrote:

Am 20.03.20 um 16:42 schrieb Jan Engelhardt:

There was talk that Fedora wanted to switch to the sqlite backend.
If that is preferable to ndb (and I would envision that the Fedora guys did
their work on the numbers), would it not make sense to skip ndb altogether?

I doubt they ever looked at nbd - Fedora's plan to move to sqlite is much
older than that. And we just as Fedora want to get rid of BDB - and the
difference is that Fedora got a plan and Tumbleweed got a new backend :)


That's not even close to true. Fedora considered moving to NDB back in
Fedora 24 (and later 25)[1].

The discussion that occurred on that topic[2] led to the integration
of the LMDB backend[3], which was then dismissed after upstream
promised to fix things for us[4] and then didn't after three years, so
it's been removed[5]. The SQLite backend was developed after giving up
on LMDB[6], and now Fedora is moving to SQLite in Fedora 33[7].

In conclusion, it was definitely considered, but it was rejected by
the community, so Fedora went with a different option.

[1]: https://fedoraproject.org/wiki/Changes/NewRpmDBFormat
[2]:
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/6TZWDVK2VGANJ25X66FH4QLXVRCH7M7D/#6TZWDVK2VGANJ25X66FH4QLXVRCH7M7D
[3]:
https://github.com/rpm-software-management/rpm/commit/ed9de1992f5e1c23e8d8dbd61325a1e0070f2c72
[4]: https://bugzilla.redhat.com/show_bug.cgi?id=1086784
[5]:
https://github.com/rpm-software-management/rpm/commit/7de982ac0957c42f228b43685d9f486e55eac331
[6]:
https://github.com/rpm-software-management/rpm/commit/07129b641b733ab30995c93e2b08d0673b9d218c
[7]: https://fedoraproject.org/wiki/Changes/Sqlite_Rpmdb

--
真実はいつも一つ!/ Always, there's only one truth!
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups