Convert RPM to TAR
Turn RPM archives into TAR. The files the package installs are kept with their paths, times and permissions.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop RPM files on the dialor turn it to pick what to do
The files inside an RPM, as a TAR.Paths, times and permissions stay. The package header does not.
What you get
One TAR file that holds the files the package installs. Each file keeps its path, its time and its permissions, so the folder layout matches what the package would put on a system.
TAR gathers files and folders into one stream and does not compress them by itself.
What it leaves behind
The header of the RPM is left out. That means the package name, the dependencies and the install scripts are not in the TAR.
If you need to know what a package requires or what it runs when installed, read that from the RPM itself. The TAR only holds the files.
When it fails
A file that cannot be parsed as an RPM stops with
input_corrupted. No TAR is produced in that case.For other archive conversions, see every RPM conversion or every TAR conversion.
RPM and TAR.What each format is.
The formats
RPM Package
Packages for Red Hat, Fedora and SUSE. A header in front of a compressed cpio archive.
- Extensions
- .rpm
- MIME type
- application
/x -rpm - Kind
- Archives
Tar Archive
Unix tape archives. Files and folders in one stream, no compression by itself.
- Extensions
- .tar
- MIME type
- application
/x -tar - Kind
- Archives
In your code.The same RPM to TAR conversion through the API, for your app or your agent.
$ cv convert archive.rpm archive.tar$ cv convert archive.rpm archive.tarQuestions.What people ask about RPM to TAR.
Yes. The installed files keep their paths, times and permissions.
No. The install scripts are part of the header, and the header is left out.
No. TAR does not compress by itself, so the output is a plain archive of the files.
The file could not be parsed. The conversion stops and gives no TAR.