Change dhparam positional args to be inherited vars, standardize naming #1263
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.
PR #913 added
DHPARAM_GENERATION
as a positional argument to generate-dhparam.sh. However, since it was the second positional argument,DHPARAM_BITS
would also have to be defined orDHPARAM_GENERATION
would be read intoDHPARAM_BITS
. This changes the arguments to be inherited variables which do not depend on order, just declaration.Also change instances of
GENERATE_DHPARAM
toDHPARAM_GENERATION
since it's unnecessary to have another variable. I thinkGENERATE_DHPARAM
is actually a better name (verb vs. noun), butDHPARAM_GENERATION
is already defined and may break someone if changed.Addresses #913 (comment)
Behavior before:
Behavior after: