<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>Changes (by Roland Haas):</p>
<p><table>
<tr><td>status:</td><td>open (was new)</td></tr>
</table></p>
<p>Currently, if you have the variable HDF5_DIR set in your shell startup file, Cactus will interpret this as a configuration option and will override whatever is set in your optionlist.</p>
<p>This behaviour occurs because the "make" utility allows you to specify options on the command line which are then converted into environment variables. This is a method for overriding options on the command line.</p>
<p>However, the fact that variables from the user's environment are also overriding the optionlist is very undesirable. It would be good if this could be fixed somehow.</p>
<p>This ticket is in response to #100.</p>
<p><strong>Keyword:</strong></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>