Hi Bernard, On Sunday 17 July 2005 00:06, Bernard Li wrote: > Hey Erich: > > Is there any particular reason why udpcast is distro-specific? I would > imagine that the one compiled under RHEL3 will work for all the other > distroes, in which case it should really be moved back to the RPMS > directory. > > I tested the RHEL3 RPM on FC3 and it works fine.
in principle almost every binary package is distribution dependent due to the required libraries and the provides/requires in the RPMs. Also noarch packages can be distro dependent, for example when something like the python version is hardwired in a script by some makefile. Now udpcast is pretty compatible as it only depends on some glibc libraries. But does every distro you can think of fulfill the requirements? distro/rhel3-i386> rpm -q --requires -p udpcast-20050226-1.i386.rpm /bin/sh libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libpthread.so.0 libpthread.so.0(GLIBC_2.0) libpthread.so.0(GLIBC_2.1) libpthread.so.0(GLIBC_2.2) libpthread.so.0(GLIBC_2.3.2) rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Right now it may, for distros currently supported by OSCAR... OTOH, how well can we test something? Can we risk that the packages compiled under one distro have rare problems under another distro because of some difference in the API or the include files which the RPM build process didn't catch? Rocks is limited to one distro, there is no such issue there. I think OSCAR should play safe and better recompile binary packages for each supported distro. But maybe I'm paranoid here, because I'm afraid of having to debug packages which I didn't develop... Additionally disturbing: keeping binary RPMs in the packages/*/RPMS directory means to mess up the /tftpboot/rpm directory with RPMs for different and useless architectures. Now we have three. It would be nicer to get really only the RPMs which are needed copied into /tftpboot/rpm. If you want to get support for heterogeneous setups (multiple architectures or distros managed by the same master node), you should better keep the architectures and distros well separated. You might want to end up with /tftpboot/rpm-rhel4-x86_64 /tftpboot/rpm-fc2-i386 and the easiest way to copy in the necessary RPMs is to have them nicely separated by distro and architecture. Best regards, Erich ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
