On Feb 6, 2008, at 10:52 AM, Jeff Johnson wrote:

>
> On Feb 6, 2008, at 10:40 AM, Stefan Westmeier wrote:
>
>> Hi,
>>
>> as I want my packages being named different than standard, I  
>> changed the naming convention by
>> setting:
>>
>> %_build_name_fmt %%{NAME}-%%{VERSION}-%%{Project}-%%{Branch}-%% 
>> {RELEASE}.x86.rpm
>> %_repackage_name_fmt %%{NAME}-%%{VERSION}-%%{Project}-%%{Branch}-%% 
>> {RELEASE}.x86.rpm
>>
>> I defined "Project" and "Branch" as additional tags via % 
>> _arbitrary_tags. Here some examples for packages:
>>
>> most-bin-1.0-refprj-tr-0802061556.x86.rpm
>> most-src-1.0-refprj-tr-0802061556.x86.rpm
>> most-trg-1.0-refprj-tr-0802061556.x86.rpm
>>
>> Using rpm -qa --qf '<some string>' showing the additional tags  
>> works fine.
>>

I missed the use of arbitrary tags, apologies. Using arbitrary tags is
superior to changing Release: itself imho, because Release: comparisons
impose additional (and complicated) constraints on how EVR comparisons
determine "newer" in order to decide whether an "upgrade" is necessary.

You can change the default query format to include %{Project} etc

# Default headerSprintf() output format string for rpm -qa
#
# XXX   Note: escaped %% for use in headerSprintf()
%_query_all_fmt         %%{name}-%%{version}-%%{release}.%%{arch}

to be
     %_query_all_fmt         %%{name}-%%{version}--%%{Project}-%% 
{Branch}-%%{release}.%%{arch}

73 de Jeff