Use env wherever preconfigopts is used to set environmental vars#2807
Conversation
…les. Without `env`, we are relying on a syntactical feature of Bourne-type shells; the `env` utility guarantees that the command-line will continue to work even with other shells (e.g., `tcsh`).
|
Automatic reply from Jenkins: Can I test this? |
|
For the record, here are the command incantations used to patch all |
env wherever `preconfigopts is used to set environmental varsenv wherever preconfigopts is used to set environmental vars
|
Jenkins: ok to test |
|
@riccardomurri up for doing the same for |
|
Easyconfigs unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/7251/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
Test report by @boegel |
|
retested most of these easyconfigs, no problems whatsoever encountered, so going in Thanks @riccardomurri! |
Without
env, we are relying on a syntactical feature of Bourne-typeshells; the
envutility guarantees that the command-line will continueto work even with other shells (e.g.,
tcsh).