Hi there,
we now use gpg for two features:
a) signing release artefacts in the release target
b) checking signatures in the verify-release target
Now
a) gets run, whenever gpg.exec points to an existing file. If so, it
prompts interactively for a password to a siging key and uses that for
the signing. Since I want to run the release target but not to do the
signing, I used to set gpg.exec to a non-existing file.
b) gets run unconditionally and is a feature I would like to use. b)
requires gpg.exec to point to an existing file.
IMHO that combination, use b) but not a), might be frequent.
I propose to add another property, gpg.sign.files, which controls,
whether a) is used. Its default will be true, does unchanged behavior
and the existence check for gpg.exec will be left in place. Setting it
to false and gpg.exec to the correct gpg path, allows to run b) without a).
I have a patch ready and if there are no objections, I will apply it
tomorrow and add a sentence to BUILDING.txt.
Best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
