RPM Community Forums

Mailing List Message of <rpm-devel>

Re: why does RPM 5.1.0 think some fulfilled dependencies are not fulfilled?

From: Jeff Johnson <n3npq@mac.com>
Date: Tue 15 Apr 2008 - 20:05:41 CEST
Message-Id: <6A9AE5AE-5484-47C7-8507-2D506F9518BB@mac.com>

On Apr 15, 2008, at 1:31 PM, Ralf S. Engelschall wrote:
>
> Yes, I'm fine if RPM 5.2 allows me to remove the "N" from SourceN.
>

Any suggestions for ordering syntax? positional rather than explicit  
indexing
has its own speshul pain.

>> Overloading %description to carry descriptive info is going to cause
>> some pain when RPM has to commit to an encoding. There's no easy  
>> way to ensure
>> that the expanded macros follow the same encoding rules as the  
>> template does:
>>
>>  %description
>>     Perl modules for general utility usage:
>>     - Alias (%{V_alias})
>>     - Attribute::Handlers (%{V_attribute_handlers})
>>     - Class::Container (%{V_class_container})
>>     - Class::Data::Inheritable (%{V_class_data_inheritable})
>
> Ok, certainly an issue, but harmless for OpenPKG as the perl-xxx  
> bundle
> packages are mostly an exception here: the usual OpenPKG package  
> doesn't
> use macros in %description as there is usually no need for this. The
> bundle packages just need to inform the user that multiple upstream
> sources are contained and hence use %description for this.
>

Actually headerSprintf(..., "%{DESCRIPTION:utf8}", ...) should sort  
the encoding
issues nicely. The macros are already expanded during parse.

73 de Jeff
Received on Tue Apr 15 20:06:55 2008
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.