Bug 15961
Summary: | Feature request rpm reads and writes manifest files | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | kestes |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | jbj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-08-16 14:29:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
kestes
2000-08-10 23:03:01 UTC
Notice that reading the archive is a bit tricky since rpm does not really have a good filename convention for naming packages so rpm will need to search the headers of each file in the archive to figure out what the package is. My package archive is quite large (5,000 files and growing) so there may need to be a chace to make this usable. Right now RPM can not write the manifest list because it does not save the command line arguments which packages are loaded into the system and rpm does not know how to print out the package names in topologically sorted order. Manifests (i.e. glob expressions contained in a file that can be used to generate a list of packages) are in rpm-4.0.3. |