On Mon, Jan 12, 2009 at 4:23 PM, Jeff Johnson <[email protected]> wrote:
> (not seen this message come through. apologies if duplicated).
>
> Begin forwarded message:
>
> From: Jeff Johnson <[email protected]>
>> Date: January 12, 2009 8:58:52 AM EST
>> To: [email protected]
>> Subject: Additional features or bug fixes for rpm-5.1.7?
>>
>> The release of rpm-5.1.7 is likely pending in the next week or two.
>>
>> Several important implementations that are ready for release were moved
>> into rpm-5.1.6+ this weekend, including
>>
>> 1) Using PCRE (which is now a MANDATORY build pre-requisite for RPM) to
>> parse dependency EVR tags and apply tag data validation patterns.
>> RPM has always been too loose about what is permitted in tag
>> content,
>> the data validation patterns will help ensure package metadata
>> reliability.
>>
>> 2) Adding signature support using OpenSSL as well as BeeCrypt and NSS.
>> All
>> three implementations are now fully supported. I'll finish up the
>> 4th
>> crypto implementation in RPM, using -lgcrypt, one of these days,
>> mostly because
>> GCrypt has support for ECDSA.
>>
>> 3) Adding --needswhat/--whatneeds generalizations of
>> --whatprovides/--whatrequires.
>> This is basically a loop over all, not just one, Provides: or
>> Requires:, and
>> helps identifying, say, "unused packages" quite a bit easier.
>>
>
It is necessary, i think, to add also the corrisponding simple macros in
macros.in.
rpm alias --whatneeds --queryformat '[%{whatneeds}\n]'
rpm alias --needswhat --queryformat '[%{needswhat}\n]'
This also in HEAD.
Regards
