New payload format
Currently used format is CPIO but it has a filesize limit of 8 GiB. This is not enough when one tries to distribute very large files, for example appliance images, packaged as RPMs. Developers will need to find a way how to enhance CPIO or try another format soon. TAR is really not an option …
Blueprint information
- Status:
- Started
- Approver:
- rpm5.org
- Priority:
- Low
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Jeff Johnson
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- Jeff Johnson
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
rpm5 already supports tar payloads (but hardlinks aren't handledcorrectly, cpio orders differently than tar w hardlinks)
rpm5 also has support for AR payloads targeted for reading *.deb wrappers.
rpm5 mostly supports XAR as well, but there's still an issue with dueling payload <-> file compressors.
Embedded nix will need the nix package format (perl -> C rewrite is needed)
rpm.org has merged the code to support a new "header less cpio" format that
permits >4Gb files (a cpio header imposed limit). The implementation adds
a uin64_t tag to headers as well as a rpmarchive utility to duplicate rpm2cpio
behavior extracting payloads from *.rpm packages.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
