Hi Matt, Hi Root, Thanks for the patch ... it came a few hours too late, as I began this weekend upgrading to RH 6.0 (ugh). One comment: Matthew D. Langston writes: > > then what is the mechanism for failure of the ROOT tarball to work? > > Many other packages work just fine like this. > > Although this idea would work in theory, I don't believe that it would > work in practice. The majority of users use their computers for many > other things besides running ROOT. It would be an unreasonable burden > on users to force them to maintain a particular configuration just so > that they could run ROOT. A software package should serve its users, > not vice versa. My view on this is that the ROOT team provides a service by providing the tarballs. Your last comment I think is turned around, though ... I would prefer that the ROOT team assume a _STANDARD_ configuration when they provide the tarball, and HOPE that any upgrades a user has done on their own would be compatible. The situation now with the 2.2.10 RedHat "5.2" tarball is that a user MUST upgrade, the standard configuration for 5.2 WILL NOT WORK with ROOT. So a user must upgrade, and this is the user serving the software package. my 0.02 (how many euros is that?) JT
This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:43:38 MET