[Einstein Toolkit] #1344: Cactus doesn't export some environment variables after changing them
#1344: Cactus doesn't export some environment variables after changing them --------------------+------------------------------------------------------- Reporter: knarf | Owner: Type: defect | Status: new Priority: minor | Milestone: ET_2013_11 Component: Cactus | Version: development version Keywords: | --------------------+------------------------------------------------------- Cactus doesn't export some environment variables after changing them. The attached patch fixes this.
#1344: Cactus doesn't export some environment variables after changing them ---------------------+------------------------------------------------------ Reporter: knarf | Owner: Type: defect | Status: review Priority: minor | Milestone: ET_2013_11 Component: Cactus | Version: development version Resolution: | Keywords: ---------------------+------------------------------------------------------ Changes (by knarf):
* status: new => review
Comment:
To be applied only after the spring release.
#1344: Cactus doesn't export some environment variables after changing them ---------------------+------------------------------------------------------ Reporter: knarf | Owner: Type: defect | Status: review Priority: minor | Milestone: ET_2013_11 Component: Cactus | Version: development version Resolution: | Keywords: ---------------------+------------------------------------------------------
Comment (by eschnett):
Is this actually necessary? It seems that #1345 indicates that the variables are already marked for export, and these additional export statements are not necessary.
#1344: Cactus doesn't export some environment variables after changing them ----------------------+----------------------------------------------------- Reporter: knarf | Owner: Type: defect | Status: closed Priority: minor | Milestone: ET_2013_11 Component: Cactus | Version: development version Resolution: invalid | Keywords: ----------------------+----------------------------------------------------- Changes (by knarf):
* status: review => closed * resolution: => invalid
Comment:
Right, what I didn't know: 'export' doesn't put the current value of a variable into the shell environment (and thus passes that to subshells), but only marks it to be passed down. Thus, one export is sufficient to always pass the current value down subshells.
trac@lists.einsteintoolkit.org
-
Einstein Toolkit