Package: mlocate
X-Debbugs-Cc: d...@gnui.org
Version: 1.1.13-1
Severity: normal

## Dear mlocate maintainer,

as of now mlocate is a transitional package to plocate.  In other words, during 
release upgrade locate upgrades from mlocate to plocate.

To the best of my understanding of Debian best practices, this is acceptable if 
either (a) a new package is a better drop-in replacement for an old one, (b) an 
old package is not passable anymore due to security bugs, that are not going to 
be fixed, or something like that.

Unfortunately, plocate is not a complete replacement, let aside being drop-in: 
mlocate(1) (unless `-A` switch is given) interprets pattern list as subject to 
OR, plocate(1) does not support OR-mode at all, only AND.

Sudden change of basic logic is definitely not what is expected from a mere 
upgrade from one version to the next one.

I do not see any severe bugs in mlocate either.

So, please bring it back to Debian.

## Dear plocate developer,

even if there are no plans to implement OR-mode (I fully agree, that it is not 
as  useful as AND-mode), why does not plocate(1) accept `-A` switch as a no-op, 
but fails with an error instead?

        $ plocate -A foo bar
        plocate: invalid option -- 'A'


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)

Versions of packages mlocate depends on:
ii  plocate  1.1.13-1

Attachment: signature.asc
Description: PGP signature

Reply via email to