<html>#1301: Formaline should store the thornlist
<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>resolved</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>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>resolved (was new)</td></tr>
</table></p>
<p>Formaline should store the thornlist used to build the configuration. This will make it easier to reconstruct a working Cactus tree from the Formaline output.</p>
<p><strong>Keyword:</strong></p>
<p>Comment (by Roland Haas):</p>
<p>Since thornlist is included in the tarball and the list of compiled thorns is also in formaline-jar.txt which contains both thorn names eg:</p>
<div class="codehilite"><pre><span></span><span>thorns/zlib="active"</span>
</pre></div>
<p>as well as arrangements:</p>
<div class="codehilite"><pre><span></span><span>thorn_arrangements/zlib="ExternalLibraries"</span>
</pre></div>
<p>all information is present.</p>
<p>Eg a:</p>
<div class="codehilite"><pre><span></span><span>awk -v FS='[/="]' '/^thorn_arrangements/{print $4"/"$2}' formaline-jar.txt</span>
</pre></div>
<p>gets the thornlist required to compile (but not to checkout which Cactus does not know anything about). That latter one is only stored on the tarball.</p>
<p>I think there is direct need to add extra code for all conceivable cases of Formaline use if that leads to extra output files and extra code to maintain.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/1301/formaline-should-store-the-thornlist'>https://bitbucket.org/einsteintoolkit/tickets/issues/1301/formaline-should-store-the-thornlist</a></p>
</html>