[aclug-L] Re: Question

["Jesse Kaufman" <glandix@xxxxxxxxxxxx>]

> I believe the split occured in RedHat 8=20

yup, i'm pretty sure that's correct

> /usr/src/redhat/RPMS/<arch>. On x86 based systems <arch> is usually
> "i386". You can just look at the output of the rpm build command at the
> end; it will tell you what rpm files it created and where they are.

don't forget about 'noarch' ... many-a-time i've compiled one of RH's 
redhat-config-* python apps and freaked because it wasn't in the i386 folder 
only to remember it got put in noarch

also, in MDK, it's /usr/src/RPM (i can't remember if whoever started this 
thread said which rpm-based distro they're using)...

> rpm -bb whatever.spec OR rpmbuild -bb whatever.spec (depending on version=

use -ba instead of -bb ... then you can distribute your src.rpm file incase 
someone else might like any changes you make :)

> rpm -ivh /usr/src/redhat/RPMS/iX86/whatever.rpm (iX86 may be i386 on to i=
> 686=20
> (or on other archs, alpha, alphaev5, sparc, etc)

the most common on an x86 platform are i386 (RH's default), i586 (MDK's 
default), i686 and athlon... they do have an i486, but i can't think of 
anywhere i've actually seen a .i486.rpm file...

also, personally (based on experience and reading) i suggest using -Uvh instead 
of -ivh...  incase your trying to install an upgraded package, it will just 
upgrade it... if not, it just installs it...


-- This is the discussion@xxxxxxxxx list.  To unsubscribe,
visit http://www.complete.org/cgi-bin/listargate-aclug.cgi