Many tools that use .d configuration directories support multiple such
directories, to make it easy to separate local sysadmin configuration
from distribution configuration. For instance, a hypothetical
apt-verify-myplugin package could install
/usr/share/apt/verify.d/50myplugin so that it automatically works when
installed, and then the sysadmin could change that with
/etc/apt/verify.d/50myplugin . One of several advantages of this is that
a sysadmin can, themselves, *package* their configuration very easily,
without having to divert files or similar.

(Also, in the process of this, you might consider refusing to run if no
configuration exists, to avoid effectively disabling verification. If a
user really wants to *disable* verification they should use the apt
configuration for *that* rather than installing apt-verify as a hook and
then giving apt-verify nothing to do.)

forwarded 1060181 https://gitlab.com/debdistutils/apt-verify/-/issues/6
tags 1060181 upstream
thanks

Josh Triplett <josh@joshtriplett.org> writes:

Thanks for feedback -- this makes sense, and I've opened an upstream bug
about it:

https://gitlab.com/debdistutils/apt-verify/-/issues/6

What do you think about processing identically named scripts in both
paths vs only the /etc/ script?

There is no way verification can be disabled -- apt will yell.  Or can
you explain more what you mean?

/Simon