Hi all, Hmm ... I'm afraid Konstantin, Kris, and Anders have missed the point. > I do not want choice. If you leave everything as default, you don't need to choose. > I do not want multiple versions. That seems unavoidable. > I do not want 100 setup scripts to run. It's one more script being sourced at login-time. That's it. No need to to anything later on. Don't you already source /home/brahmlib/brahms_setup.csh somewhere in your login scripts? If not, I'm not surprised you have all those problems, since that means you have to keep up with things your self, which is a hazzle. > The one problem I see is if we keep root/pro as close to the current > version of root as possible, doesn't that mean that things will > change often which will lead to people frequently having something > that worked yesterday that does not work today? Often we need a very recent version of ROOT, since we often like to use the new features offered by recent ROOT, hence _our_ pro should probably not nessecarely follow the ROOT pro. More likely, we'd have pro point to the second last version of ROOT. Most of the time (though not always, as when ROOT shifted from global pointer gXW to gVirtualX, and similar), ROOT revisions within the same minor version are fully compatible, that being changed most of are additions, hence I don't think that will be a big problem. Here at NBI, I try to make sure that the BRAT pro is build using the ROOT pro, and if I update ROOT pro, then I rebuild BRAT. The same goes for new (in fact, it goes for new more then anything else). Anyway, this has really nothing to do with login scripts. What I offered was a convinient way for the user to choose, if that's needed! If no choice is needed, the default behaviour should surfice. In fact, many of the choices are made behind your back (with the _possibility_ of overloading). > We should avoid always being hunting for the latest version of > everything. For the reasons Kris gives. I'm not sure that's what Kris meant Anders. In fact, I think Kris really advocates is consistency between ROOT and BRAT versions. In fact, I think we will do porly, if we stuck with the ROOT pro version all the time, since updates/bug corrections are slow in this branch. If you really feel strongly on having _stable_ ROOT versions, why don't you just use the ROOT teams binary ROOT avaliable via AFS? I don't think it's possible to give any kind of rule as when to update ROOT, not even a rule of thumb. If there must be one, however, I think it must be this: "Update ROOT when needed for features and bug corrections, recompile BRAT using that ROOT, and move pointers old/new/pro for both BRAT and ROOT." Cheers, Christian ----------------------------------------------------------- Holm Christensen Phone: (+45) 35 35 96 91 Sankt Hansgade 23, 1. th. Office: (+45) 353 25 305 DK-2200 Copenhagen N Web: www.nbi.dk/~cholm Denmark Email: cholm@nbi.dk
This archive was generated by hypermail 2b29 : Mon May 29 2000 - 04:35:59 EDT