[ET Trac] #1301: Formaline should store the thornlist

Roland Haas trac-noreply at einsteintoolkit.org
Tue Jan 25 16:12:04 CST 2022


#1301: Formaline should store the thornlist

 Reporter: Ian Hinder
   Status: resolved
Milestone: 
  Version: 
     Type: enhancement
 Priority: minor
Component: Cactus

Changes (by Roland Haas):

status: resolved (was new)

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.


**Keyword:**
Comment (by Roland Haas):

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:

```
thorns/zlib="active"
```

as well as arrangements:


```
thorn_arrangements/zlib="ExternalLibraries"
```

all information is present.

Eg a:

```
awk -v FS='[/="]' '/^thorn_arrangements/{print $4"/"$2}' formaline-jar.txt
```

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.

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.

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1301/formaline-should-store-the-thornlist
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einsteintoolkit.org/pipermail/trac/attachments/20220125/688c5a89/attachment.html 


More information about the Trac mailing list