[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: About ROOT [Was: Re: ROOT as A replacement for gnuplot]



Hi Christian,

On 9/16/05, Christian Holm Christensen <cholm@nbi.dk> wrote:

Some one suggested that the plugins should really live in it's own
source tree, and I couldn't agree more.   However, as things are now,
that's really not an option for ROOT.  The main thing being, that the
plugins depend on being in the main source tree.  Ideally, upstream
would make a `core' ROOT source tree, and have plugins live in their own
CVS repository, and build-depend on the ROOT core.  I've suggested this
to upstream, and even though they are not entirely dismissive, they seem
not to be too eager either.   In fact, if they did that, upstream would
get rid of a lot of problems that they currently have.  Ah well.   Lobby
for this on roottalk@root.cern.ch if you please.

Here's another reason to modularize the plugins into separate source packages (once ROOT is accepted into Debian) that I hope will help you convince upstream.  Right now they depend upon everything from Qt to MySQL to LDAP.  That is going to be a horrible pain to keep up-to-date with respect to third-party library transitions.  ROOT will find it very difficult to get new releases into the "testing" distribution of Debian as long as plugins built from its source package depend upon so many different libraries.  Since testing is the main path into stable, this may result in new stable Debian releases shipping with a version of ROOT that is already out-of-date at the time of the release.  I'm sure no one wants to see that.

Any chance it's possible to package the plugins as separate source packages in Debian even though they are shipped in the ROOT source tarball by upstream?

best regards,

--
Kevin B. McCarty <kmccarty@princeton.edu>   Physics Department
WWW: http://www.princeton.edu/~kmccarty/    Princeton University
GPG: public key ID 4F83C751                 Princeton, NJ 08544
Reply to: