Re: Different "Release" numbers in binary and source RPMs?

["Mike A. Harris" <mharris meteng on ca>]

On Thu, 28 Sep 2000, Alexey Nogin wrote:

>> %define release 1rh%([ -f /etc/redhat-release ] && cat /etc/redhat-release |awk '{print $5}' )
>>
>Yes, sure, I have
>%define rh_release   %(rpm -q --queryformat '%{VERSION}' redhat-release)
>but that's not the problem...
> 
>> So you'd end up with:
>> 
>> package-1.0.0-1rh6.2.src.rpm - on a 6.2 system.
>>
>Yes, and that's the problem - my question is how do I end up with
>1.rh6.2.i386.rpm _and_ 1.src.rpm? I do not want to have the RH release 
>number in the name of the source RPM since it gives people a misconception
>that it wouldn't build on other versions of RH.

The name-version-release is the identifying part of the package
name.  Whatever the source package name-version-release is the
resulting arch files will become as well.  If you want to build
for different RedHat versions, create a script to modify the spec
before the build.  This is often done using a package.spec.in
file and having awk or sed modify the release number accordingly.

What you're trying to do is not possible I don't believe, and if
it were it would cause confusion as people with the
package-1.0.0-1rh6.2.i386.rpm would look for a source RPM named
package-1.0.0-1rh6.2.src.rpm, but yours wouldn't be called
that.  That goes against what the release number is meant for.

TTYL


--
         Mike A. Harris  -  Linux advocate  -  Open source advocate
                   Copyright 2000 all rights reserved
                               ----------
[Quote: Linus Torvalds - Aug 27, 2000 - linux-kernel mailing list]
"And I'm right.  I'm always right, but in this case I'm just a bit more
right than I usually am." -- Linus Torvalds