Subject: [NTLUG:Discuss] more rpm madness, and advice needed

[Kyle_Davenport@compusa.com]

I do all the time.  Assuming you upgraded all the dependencies for rpm4,
you  should be running "rpm --rebuild package.src.rpm".   However, most of
the time, this is not worth the trouble. Going from 6.2 to 7x changes lots
of package dependencies - even a src.rpm will have prereqs that will
conflict with your package structure in 6.2.   Sometimes it's easier going
to the homepage for the package, or finding a 6.2 contrib package.   Final
resort is to "rpmcpio package.src.rpm > package.cpio", unpack to a work
directory, and build yourself.

My odds have been about 80% successful, and less for optimizing the build
(--target=i686).  Some build tools have also changed between 6.2 and 7.x.

__________________________________________
From: krannen at gte.net

>So now I'm in a maze of twisty passages all different because when I find
>these extra rpms I need, I'm finding them in the newer rpm-4.0.2 format
>instead of the original RH6.2 rpm-3.0.5 format.  At first glance it all
seems
>OK, until I go retrieve a SRPM file and find that the newer rpm4 will not
>build anything!  Yes, my much sought after and man page gleaned "rpm -bc
>whatever.spec" command will no longer work!  (it's definitely a conspiracy
:-)
>  To make matters worse, the man pages says that's legal, but the command
>itself (and its usage statement) say it's not, and offer no build
commands.
>ARRRGGHH!  I really would like to virtually pound someone...may be time to
>play Doom for awhile to relieve my frustration. :-)

>Has anyone managed to build binaries from a SRPM using rpm4?  That should
be
>the version in upgraded 6.2 and probably all 7.x releases.  (I don't have
7.0,
>but it's there in 7.1 for sure.)