rpms/lastfm/F-9 lastfm.spec,1.1,1.2

Rex Dieter rdieter at math.unl.edu
Tue Aug 5 14:43:31 CEST 2008


Thorsten Leemhuis wrote:
> On 30.07.2008 18:09, Sergio Pascual wrote:
>> Author: sergiopr
>>
>> Update of /cvs/free/rpms/lastfm/F-9
>> In directory se02.es.rpmfusion.net:/tmp/cvs-serv19968
>>
>> Modified Files:
>>     lastfm.spec Log Message:
>> * Wed Jul 23 2008 Sergio Pascual <sergio.pasra at gmail.com> 
>> 1.4.0.56102-3
>  > [...]
>> - Vendor changed to rpmfusion
>> [...]
>>
>> Index: lastfm.spec
>> ===================================================================
>> RCS file: /cvs/free/rpms/lastfm/F-9/lastfm.spec,v
>> retrieving revision 1.1
>> retrieving revision 1.2
>> diff -u -r1.1 -r1.2
>> --- lastfm.spec    23 Jul 2008 06:22:11 -0000    1.1
>> +++ lastfm.spec    30 Jul 2008 16:09:37 -0000    1.2
>> @@ -2,7 +2,7 @@
>>  
>>  Name: lastfm
>>  Version: 1.4.0.56102
>> -Release: 2%{?dist}
>> +Release: 3%{?dist}
>>  Summary: Last.fm music client
>> [...]
>> -desktop-file-install --vendor="livna" \
>> +desktop-file-install --vendor="rpmfusion" \
> 
> Do we want to do that (here and everywhere)? Quoting from
> http://fedoraproject.org/wiki/Packaging/Guidelines
> 
>>     * If upstream uses <vendor_id>, leave it intact, otherwise use 
>> fedora as <vendor_id>.
>>     * It is important that vendor_id stay constant for the life of a 
>> package.
>> This is mostly for the sake of menu-editing (which bases off of 
>> .desktop file/path names). 

This is one danger of introducing artificial vendors.  I'm working with 
Matthias Classen (fedora desktop, gtk fame) to draft new guidelines to 
discourage this practice.

In the meantime, for any particular Fedora release, it's still a good 
idea to make a best effort to keep the vendor constant.  You can 
consider changing it for F-10+ if you like...

-- Rex


More information about the rpmfusion-developers mailing list