[Developers] Out-of-the-box compilable ThornList

[Thomas Radke]

Erik Schnetter wrote:
> On Monday 06 June 2005 14:37, Steve White wrote:
> 
>>==========================
>>What can we do about this?
>>==========================
>>
>>One solution would be to relocate thorns that require uncommon
>>libraries and environments; these would be available in a separate
>>download.
>>
>>Is it possible to educate the mechanism which builds the initial
>>ThornList to comment out thorns for which the user's environment is
>>insufficient?
> 
> 
> I think this is a good idea.  We could put an explicit list of "iffy" 
> thorns into the script that creates the initial thorn list.

I personally never used the feature of having Cactus generate a 
thornlist of all thorns available in all the arrangements that I have 
checked out.

What I'd find more practical is to start from a given parfile (that's 
what you want to run in the end), then

  (1) generate a thornlist from it using the MakeThornList script
      and a master thornlist
      Currently the latter two live somewhere else in CVS, we could just
      move them into Cactus.

  (2) check out the necessary thorns using GetCactus
      Again, this script could be moved from Utilities/Scripts/ in
      the /cactus CVS repository into lib/sbin/.

  (3) build a configuration from it

Of course, beginners should start with a very simple parfile (like 
wavetoy), with basic thorns requiring no external libraries etc.

When a configuration is to be build which has no thornlist yet, Cactus 
shouldn't just generate one with all the thorns it finds. Instead it 
could ask for a parfile (similar to running a testsuite: ask for 
arrangement->thorn->parfile) which should be used to build the thornlist 
and configuration from.


-- 
Cheers, Thomas.