<html>#332: Cactus should not interpret environment variables as configuration options
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Ian Hinder</td></tr>
<tr><td style='text-align:right'> Status:</td><td>open</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>Cactus</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Pull request is here:</p>
<p><a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactus/pull-requests/110/cactus-do-not-use-env-vars-for-config" rel="nofollow">https://bitbucket.org/cactuscode/cactus/pull-requests/110/cactus-do-not-use-env-vars-for-config</a></p>
<p>Note that this changes documented behaviour and I myself would not actually be in favor of doing so (even though am providing means).</p>
<p>Please review.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/332/cactus-should-not-interpret-environment'>https://bitbucket.org/einsteintoolkit/tickets/issues/332/cactus-should-not-interpret-environment</a></p>
</html>