[Rivet] Problem with --disable-analyses --> Solution included!

[Andy Buckley]

On 12/12/13 22:00, David Hall wrote:
> Hi Andy,
> 
> Glad it helped! (I didn’t suggest to remove testCmdLine.sh from the
> tarball though - just remove it from the list of tests when
> —disable-analyses is used)

Yep, I included that bit, but the conditional adding to EXTRA_DIST would
have removed it from the tarball, too.

> I think —disable-analyses is particularly
> useful for personal computers to limit the installation size/time, if
> you just want to test your own analyses,

Good point. We've never been in that situation, hence the brokenness
passed us by!

If you have any bright ideas about how we could maybe distribute
analyses separately from Rivet (cf. LHAPDF6 data files) then let us
know, but every time we think about it we get stumped by umpteen awkward
side-effects, plus there is some value to having Rivet as one
well-defined collection of tools and analyses. We're pretty well
established now, though, and at some point the number of analyses really
might be too unwieldy...

Andy


>> Hi David,
>>
>> Thanks for the step by step guide ;-) I've put this into the development
>> trunk now, with the sole exception of the very last part: I think we
>> still want to bundle testCmdLine.sh in the tarball even if (for some
>> weird reason) the person making the tarball happened to have been
>> working in no-analyses mode. Let me know if I guessed wrong somehow!
>>
>> Andy
>>
>> -- 
>> Dr Andy Buckley, Royal Society University Research Fellow
>> Particle Physics Expt Group, University of Glasgow / PH Dept, CERN
> 


-- 
Dr Andy Buckley, Royal Society University Research Fellow
Particle Physics Expt Group, University of Glasgow / PH Dept, CERN