Fwd: Additional features or bug fixes for rpm-5.1.7?

Mon, 12 Jan 2009 07:23:17 -0800 

(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.
4) Adding an additional tsort relation to guarantee that new packages are installed before old packages are erased. The additional "install-before- erase" relation cures a number of flaws installing packages if/when dependency loops are encountered.
Additional bug fixes associated with the above functionality were moved from development HEAD to rpm-5.1.6+ as necessary, but there may be other 
desired bug fixes that should also be moved.

Are there any other features or bug fixes that anyone wants added to
rpm-5.1.7 before release?
Last night's (or tonight's) snapshot should contain the release candidate code. 

73 de Jeff

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to