Refactor directive validity checks
authorJacob Bachmeyer <jcb@gnu.org>
Thu, 27 Oct 2022 00:24:56 +0000 (19:24 -0500)
committerJacob Bachmeyer <jcb@gnu.org>
Thu, 27 Oct 2022 00:24:56 +0000 (19:24 -0500)
commit86b458910ddda2c227622cafa3c37b10682d0561
tree13795fad5fb5551b0680e7d002bf448f197fa8f3
parentcb57100fe7f167ad577baa2bb3e5c677934b8d13
Refactor directive validity checks

The check for the "replace" element appearing in a v1.1 directive is moved
to interpret_directive and directive processing no longer stops at the
first error, since the documentation states that the order of directive
elements is insignificant.

This also fixes a long-standing bug that resulted in the sending of email
to the registered maintainers for a package depending on the relative
location of the "directory" element; the testsuite is adjusted accordingly.
gatekeeper.pl
testsuite/gatekeeper.all/03_triplet.exp