[Rivet] Warning: change to analysis loader!

[Frank Siegert]

Hi Andy,

Andy Buckley, Friday 28 August 2009:
> Be careful about updating Rivet SVN at the moment: today I made some
> major commits which break backwards compatibility and will probably
> interact unhappily with existing installations.
>
> The changes consist of a new analysis plugin loader system which
> reduces the boilerplate code required when writing an analysis
> (including removing the need for analysis header files), and also make
> it easier to split the plugin analyses into multiple per-expt
> libraries. The new loader system now only loads plugin libraries of the
> form Rivet*.so, (i.e. the old name lib*Rivet*.so won't be loaded) and
> the loading mechanism and API are completely different. The
> AnalysisLoader package also changed, so the bundled pyext files will
> break: for now, please either use HepMC 2.5, for which I've done the
> update, or delete the rivet_wrap.cc* and rivet.py* files.

Thank you very much for this great improvement in the analysis loader 
mechanism, it looks very elegant. I have fixed a small remaining issue 
with the JADE_OPAL analyses, and it seems to be working nicely at a first 
glance now. I have a couple of related questions:

- Out of curiosity: What is the reasoning behind moving the analyses into 
separate subdirectories/libraries?

- Is there any practical reason for moving from libRivet*.so to Rivet*.so? 
The old version seemed to make sense to me, as it is a library after all.

- In the doc directory, building currently fails with the message
    Tried to register a second plugin analysis called ''
This happens because it tries to read files like
[...]/trunk/src/share/Rivet/CDF_2009_S8233977.info
when ../src/.libs is in the LD_LIBRARY_PATH due to binreloc I suppose. Do 
you have any idea how to work around this?

Thanks,
Frank