Hi Erich: It seems like you replied to both my emails in one shot :-)
> if you look at the "requires" of the RPM (and if they are > correctly built, > i.e. not set manually) you'll usually see that the RPM > depends on particular > glibc versions (at least). Of course it is possible that the > NOW supported > distros fulfill all the requirements, but I doubt this is > generally valid for > any RPM based distro which we might support. I'm for > rebuilding the RPMs. That > saves us from trouble which is hard to debug. Besides, svn > cannot handle > symlinks, AFAIK. > > BTW: I doubt the three fedora core generations (2,3,4) can > share RPMs. RHEL3 > and RHEL4 usually can't. My only concern is that this will make our tarball really bloated as we continue to support more distributions. But I guess for now I will just duplicate the RPMs. > Some of the packages where there was a chance to get them > from the distro, > too, were renamed. For example from mpich to mpich-oscar. Why > don't we do it > the same way with pvm? Then there is no ambiguity on what we > want to install. I suppose this would work, what does the ORNL crew think? But I guess this would cause a problem if the user already has "pvm" installed. This is sort of the same as tftp-server vs atftp-server. Cheers, Bernard ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
