Convert XAR to TGZ
Turn XAR archives into TGZ. Every stored file is kept as it is, so an installer package gives its Bom, PackageInfo, Payload and Scripts parts with the payload still packed.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop XAR files on the dialor turn it to pick what to do
An installer package opened into a TGZ.Every file inside the XAR comes out as it is, in one gzipped tar archive.
What you get
One TGZ file. The files stored in the XAR are kept as they are and placed in a tar archive, which is then compressed with gzip.
For a macOS installer package, that gives you its Bom, PackageInfo, Payload and Scripts parts as separate items in the archive.
What stays packed
The conversion unpacks the XAR container, not what is inside it. In an installer package, the Payload is still packed in the TGZ, just as it was in the XAR.
When it fails
If the XAR cannot be parsed, the conversion stops with
input_corrupted. No TGZ is made in that case.To go the other way, use TGZ to XAR.
XAR and TGZ.What each format is.
The formats
XAR Archive
The archive behind macOS installer packages.
- Extensions
- .xar .pkg
- MIME type
- application
/x -xar - Kind
- Archives
Gzipped Tar Archive
Gzip-compressed tar archives, the way source code ships.
- Extensions
- .tgz
- MIME type
- application
/gzip - Kind
- Archives
In your code.The same XAR to TGZ conversion through the API, for your app or your agent.
$ cv convert archive.xar archive.tgz$ cv convert archive.xar archive.tgzQuestions.What people ask about XAR to TGZ.
You get one TGZ with the package's Bom, PackageInfo, Payload and Scripts parts inside. The Payload is still packed.
No. Every stored file is kept as it is. Only the container changes, from XAR to a gzip-compressed tar archive.
No. The Payload stays packed, exactly as it was in the package.
The file could not be parsed as a XAR archive. When that happens, the conversion stops and gives no TGZ.