Accept old mixed-case toolchain_env_var variable names #729
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.
See #728 and #687.
Having done this, though, I wonder if having the toolchain env vars be uppercase would be better in general, even if we maintain an old/deprecated mixed-case name? All the tool overrides are already in uppercase, and using all-uppercase environment variables is a widely used convention. We could extend
deprecated_toolchain_env_var
to cover bothNMIGEN_ENV_Diamond
andAMARANTH_ENV_Diamond
, withAMARANTH_ENV_DIAMOND
being the nominal name, used first if multiple are set.I don't especially mind, happy to just take this as-is (or with whatever changes you want), but maybe it would be more consistent to deliberately change to all-uppercase for 0.4.