<html>#2379: simfactory's @ENV(FOO)@ syntax in option list does not have accees to env from envsetup
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>SimFactory</td></tr>
</table>
<p>Simfactory supports expanding env variables using a syntax <code>@ENV(FOO)@</code> to access <code>$FOO</code>. This fails to work as expected in option lists in that it cannot access environment variables set by simfactory’s <code>envsetup</code> command, which is typically used to load modules on clusters.</p>
<p>This likely is due to simfactory not executing <code>envsetup</code> when it sets up the <code>OptionList</code> and instead only doing so when executing <code>make sim-config options=OptionList</code>.</p>
<p>A workaround is to use bare Cactus methods to use <code>${FOO}</code> in the option list, which is handled by Cactus' setup phase at which point <code>envsetup</code> has executed.</p>
<p>This effect sciama.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2379/simfactorys-env-foo-syntax-in-option-list'>https://bitbucket.org/einsteintoolkit/tickets/issues/2379/simfactorys-env-foo-syntax-in-option-list</a></p>
</html>