Hi Jacek, I corrected most of your bug reports in the latest release of the ROOT 2.23.12 RPMS (the availability of which will be announced shortly). In particular, the SRPM now respects the users setting of CERNLIB. Also, the convenience symlinks to the root utilitues (i.e. root, h2root, etc.) are not made if an earlier version of ROOT is already installed on the users system. As you correctly point out, this lets users "test drive" a newer version of ROOT without changing a user's default version of ROOT. As far as your problem with the libstdc++ shared library, the new 2.23.12 RPMS only require libstdc++-libc6.1-1.so.2, which is installed by default on RedHat Linux 6.1 Intel. Thanks for your bug reports. Let me know if you have problems with the newer RPMS. -- Matthew D. Langston SLD, Stanford Linear Accelerator Center langston@SLAC.Stanford.EDU ----- Original Message ----- From: "Jacek M. Holeczek" <holeczek@us.edu.pl> To: "Matthew D. Langston" <langston@SLAC.Stanford.EDU> Cc: <roottalk@pcroot.cern.ch> Sent: Friday, January 21, 2000 3:08 AM Subject: Re: ROOT 2.23.11 RPMS available for RedHat Linux 6.1 Intel > Hi, > Just some small additional notes to my previous mail. > As I have already mentioned I was not able to install your i386.rpm > because of failed dependencies : > libstdc++-libc6.1-2.so.3 is needed by root-2.23.11-1 > I have just tried to rebuild the package, then install the newly created > i386.rpm and ... the error is still there :-) > You could warn people that they should use "--nodeps" when installing or > upgrading (concerns i386.rpm for egcs-1.1.2). > While rebuilding, I have found that it completely ignores my CERNLIB > setting (it sets "CERNLIB=/usr/local/cern/2000/lib"). You could consider > checking the user's CERNLIB setting. > After I finally installed the package, I have found that it created some > symbolic links in the "/usr/bin". I'm not sure, but I think it should > create/replace these symbolic links only if I do "upgrade", not "install". > As far as I understand you mail, the purpose of install is to test the new > root without REPLACING the existing one (and the user is responsible for > setting one's PATH). Only the upgrade should create/replace these "global" > symbolic links. > Best regards, > Jacek. > >
This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:19 MET