On 10/05/2021 11.06, Steinar H. Gunderson wrote:
On Mon, May 10, 2021 at 10:45:44AM +0200, Andreas Beckmann wrote:
Note that plocate is meant to be able to be installed alongside mlocate,
so Breaks: is not appropriate. But they share updatedb.conf (they read it
using the same code).
what do you expect to happen with updatedb.conf if both mlocate and plocate
are installed and thereafter plocate gets purged?
One would hope it's kept. But if dpkg can't handle that, maybe either I
misunderstood the dpkg developers, or it is simply a bug.
There is no concept of "shared" ownership of files (except for
multi-arch:same packages, maybe #dpkg-dev thought about that).
What is a good alternative? Can I “give it back” to mlocate in prerm if
mlocate is installed?
Looks like a '$foo-locate-common' package is needed owning the conffile
and its manpage and then have ?locate depend on it. (What about plain
locate? Does it use the same config file, too? 'locate-common' looks
like it would belong to 'locate's namespace.) Perhaps updatedb-common?
Andreas
