Made the default GPG config file overridable #48
Closed
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.
Allowed the user to be able to choose a different default GPG config file during key creation while keeping the current one as default.
In order to do this, I created a method called
configure_config_file
that takes theargs
and thegpghome
directory and creates the config file by copying the default gpg config file which can be either the default one in/usr/share/gnupg/gpg-conf.skel
or a user selected one to a new file and appending theGLEP:63
requirements in it.That way the user can decide which GPG key configuration to use while still keeping the mandatory
GLEP:63
requirements.