On Fri, 16 Nov 2001 11:09:10 -0600 ABrady <[EMAIL PROTECTED]> implied:
> On Fri, 16 Nov 2001 23:29:36 +0700 > AD Marshall <[EMAIL PROTECTED]> implied: > > > Does anyone know a good reference that explains the differences > between the above types of rpm, how each kind differs in usage and what > the effects of using an rpm that doesn't match your distro or ix86? > > > > Of course, if you want to write your own explanation, we'll take that > too. ;) > > Theoretically, noarch will install on ppc, alpha, ix86, etc. I presume > this to be correct in the absence of any evidence to the contrary. > Others may have more info. > > Those with .src.rpm are also referred to as SRPMs. They're source with > specfile contained. (This is different from, say kernel-source RPMs.) > They can be installed and worked with in that respect (usually patched, > specfile modified, configuration changes, etc), Then a simple 'rpm -ba > <specfile>' or 'rpm -bb <specfile>' will build what the diddler wanted > when making changes. Also, the SRPM can be used to simply build a binary > RPM that has better optimizations. Typing 'rpmbuild --rebuild <srpm> > --target <target>' will accomplish this. An explanation for these > options can be located through the rpm manpage. Unlike binary RPMs, you > can reinstall the SRPM multiple times without it complaining about > already being installed. It basically puts a file or files in > /usr/src/redhat/SOURCES and one in /usr/src/redahat/SPECS. I mixed things above slightly. On older RPM versions 'rpm --rebuild <yadda>' and 'rpm -bb <yadda>' was used. On later versions it was changed to 'rpmbuild --rebuild <yadda>' and 'rpmbuild -bb <yadda>' and 'target=<target>' which is old format became 'target <target>' instead. Mixing those can cause problems. > Those with the i386.rpm extension work with intel chips as well as amd > and others. ONLY with these. They shouldn't even install if you try to > put them on a different architecture. Using the SRPMs above can change > these to i486, i586, i686 and athlon. Lower chipset numbers in the RPM > (lower optimization) will work with higher level chipsets. The converse > will fail. > > Trying to use SuSE RPMs with Redhat usually won't work. Sometimes it > will. That applies to other distros as well, though more Mandrake > binaries work with Redhat than the others. Different distros place files > in different places and then have religious wars with each other over > which is "proper" and who therefore is smarter and better. I'll leave it > with this: I've tried others and had far fewer problems with Redhat > (excepting 5.1 and 7.2) than any of the others. If libraries aren't in > paths that are set for your system, they won't work. If they install and > go to the right places, they still might not work due to conflicts with > things already installed. Various vendors check conflicts and > dependencies in different ways and may not catch the problems being > created at install time. > > Trying to build the SRPMs of other distros almost all fail on Redhat. > The exception is some Mandrake do pretty well, and I've had personaly > luck with one or two from SuSE. All others failed miserably for me and > likely yield similar results for others. > > Some of this can be gleaned from the rpm manpage. Some can be garnered > from Maximum RPM (it's available for download), which is sorely out of > date. Some can be found in various other documents in various other > places around the internet. > > -- > I thought I wanted a career, turns out I just wanted paychecks. > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list -- 0 and 1. Now what could be so hard about that? _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
