Allow GPGFinder to work with nonstandard GPG version strings #888
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
This changes GPGFinder to allow for nonstandard version strings.
Specifically, I have MacGPG installed instead of upstream GPG, which results in the version string reading
gpg (GnuPG/MacGPG2) 2.2.17
instead of the expectedgpg (GnuPG) 2.2.17
Checklist
AUTHORS
I'm not sure if the unchecked items are applicable. A unit test could probably be added, though I'm not entirely sure how other than possibly making a mock binary that responds to
--version
with the MacGPG version string and adding it to the test-bins.