Hi Bernard, 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. 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. Regards, Erich On Thursday 24 November 2005 01:40, Bernard Li wrote: > Since Erich updated PVM's package directory structure to conform with > generic-setup, the setup script was not updated (to use generic-setup). > I could fix that but one of the "features" of the current setup script > is that it unlinks the distro provided PVM RPM from /tftpboot/rpm - > generic-setup does not provide this functionality though... > > What do you guys want to do about this? > > 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_id=7637&alloc_id=16865&op=click _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
