On Thu, Dec 24, 2020 at 9:34 AM Jan Engelhardt
On Thursday 2020-12-24 13:56, Neal Gompa wrote:
That [all] 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
db5 debuted in 2011, a time when, I would speculate, openSUSE was fresh out of the project oven and had other issues to focus on.
The bdb project was not very vocal about its releases either. The mailing list announcements go like 5.1.25, 5.2.28, 5.2.36, 5.3.15, 5.3.21, 6.0.19, 6.1 .. Interim releases existed, but unless you visited the homepage regularly, you would not know.
db 6.0.19 (announced 2013-06-10) was noticed. Packages like python-bsddb, clisp, etc. quickly gained patches to support the DB5/DB6 API at my hands. Many packages did not need change, which was nice. By 2013-06-16, db6 itself made an appearance in a develprj (following all the db6-enablement elsewhere).
6.0.21, the first AGPL version, soon followed (something like July) and following up felt unrewarding, so no one did the final switch of the BuildRequires.
Which is to say: If the 10-year vintage of db 4.8.30 is a problem to you, we do have the option to switch to the not-quite-so-old 7-year vintage 6.0.19. ;-)
Besides, wouldn't bdb fall under the System Library provision anyway?
For RPM systems, yes. For everyone else, no. :) -- 真実はいつも一つ!/ Always, there's only one truth!