Bug 1779190 - Remove libdb dependency from sdb package
Summary: Remove libdb dependency from sdb package
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: bind
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Menšík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1778802 1940404
TreeView+ depends on / blocked
 
Reported: 2019-12-03 13:40 UTC by Filip Januš
Modified: 2021-03-18 11:33 UTC (History)
8 users (show)

Fixed In Version: bind-9.11.13-4.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1940404 (view as bug list)
Environment:
Last Closed: 2019-12-03 18:36:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Filip Januš 2019-12-03 13:40:34 UTC
Description of problem:
According to more restrictive libdb licence policy exists effort to remove libdb's dependencies.
bind-sdb package is now built with libdb requirement, it's used as external cache database, instead of Berkeley DB is possible to use other database (MySQL, PostgreSQL,...) or directly filesystem(--with-dlz-filesystem=ARG).


Actual results:
require libdb

Expected results:
don't need libdb

Comment 1 Petr Menšík 2019-12-03 15:08:59 UTC
I have no information about named-sdb usage and popularity of any databases. I personally doubt Berkeley DB would be among popular usages of named-sdb builds.

On Rawhide, I build already DLZ plugins. They are loadable modules intended to replace statically built named-sdb.

I have no reason to keep db interface if its license is problematic. Also, bind already uses lmdb database, which might be able to replace file based storage. named-sdb have poor performance anyway, compared to bind-dyndb-ldap. I think LDAP and SQL databases are more important.

Comment 3 Petr Menšík 2019-12-03 18:36:43 UTC
Keeping possible support intact, use fedpkg local --with BDB for build with Berkeley DB support. New default is no libdb support.


Note You need to log in before you can comment on or make changes to this bug.