feat(BSS-2): cleanup env handling during build

Until now we just "set" env vars during the build of BSS-2 modules ignoring the previous value. Now we modify the env vars to keep module-system-based modifications "alive".)

@elmath this mightshould help with the build issues where an untracked dependency on pscom was only implicitly available via an loaded module (i.e. spack doesn't know about it, i.e. we have to make sure that the module-provided env var modifications are still present during the build).

added 1 commit

• 4b1e1422 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• 8314b478 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• 24c03e7d - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• b92b2114 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• c0ce46d5 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• 139c82d7 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• 8eeb6e40 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• 488e9556 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• 2f1aa868 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• fd31d898 - feat(BSS-2): cleanup env handling during build

Compare with previous version

added 1 commit

• 5bfdde2e - feat(BSS-2): cleanup env handling during build

Compare with previous version

mentioned in issue #54 (closed)

added 1 commit

• aea50674 - feat(BSS-2): cleanup env handling during build

Compare with previous version

resolved all threads

merged

mentioned in commit b64c2519