<html>#2397: incorporate envssetup into Cactus option list
<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>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p><span class="ap-mention" data-atlassian-id="557058:1671c5c3-29cc-4e83-9850-a152d33a6235">@Steven R. Brandt</span> points out that this envsetup will also have to be propagated to submit and run scripts. Likely requiring simfactory to parse the cfg file for envsetup.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2397/incorporate-envssetup-into-cactus-option'>https://bitbucket.org/einsteintoolkit/tickets/issues/2397/incorporate-envssetup-into-cactus-option</a></p>
</html>