On 07/11/2025 13:09, Rémy Maucherat wrote: <snip/>
Maybe this could be better. Why does gpg.exec gets set into build.properties.release ? I had forgotten it was also set there. Proposed changes: - Comment out gpg.exec from build.properties.default (it always needs to be set in build.properties).
Maybe set it to gpg rather than commenting it out so if gpg is on the path, the developer doesn't need to do anything.
- Don't set gpg.exec in build.properties.release, it only indicates a path on the local machine, not a version number or something needed to reproduce. Unless I missed something ...
+1 (also unless I missed something)
- "ant verify-release" should try "common" paths for gpg, maybe "/usr/bin/gpg", "/usr/local/bin/gpg", "C:/Program Files (x86)/GnuPG/bin/gpg.exe", unless there is a defined gpg.exec property.
+0. The looks like the sort of thing that ends up needing quite a bit of configuration in Ant. I think I'd lean towards if it isn't on the path, set it in ${user.home}/build.properties.
Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
