[Pkg-pdns-maintainers] Bug#701798: pdns-server package depends on libsqlite3-0 for no practical reason

Nikolay Shaplov dhyan at nataraj.su
Mon Mar 4 06:49:41 UTC 2013


> >> The bindbackend, which is part of pdns-server 3.1, uses sqlite3 for
> >> key storage.
> > 
> > So a system running without libsqlite3-0 with bind backend won't be
> > able to do DNSSEC? Would it fail gracefully or fatally in that
> > situation?
> I'm pretty sure the answer is 'fatally'.
More correct answer is bind plugin will fail if there is no libsqlite3-0 lib.

Right now I have a custom build of pdns 3.1 without any backends exept gpgsql

When it is configured to work with gpgslq everything works well.

I think it is a bad idea to include bind plugin in base package, because there 
is no way to throw it out when it is not used.

Moreover, when I updated pdns 3.0 with normal pdns 3.1 everything stopped 
working because installer brought bind plugin configuration that overrided my 
own pgsql configuration...

I think that wise edition would be following:

1. Move bind plugin into separate package
2. Create meta-package pdns-backends, that represents any possible backend. If 
no particular backend were specified during installation or were not installed 
before. 

This will allow to create workable instance during first install, remove 
libsqlite3-0 when it is not needed, and be sure that other updates will not 
bring bind backend and it's configuration on future updates.

So please do not close this bug. This bug seems to be more important then I 
think when I reported it :-)



More information about the Pkg-pdns-maintainers mailing list