[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[task #15699] Unified format for software tarballs

From: Antonio Diaz Diaz
Subject: [task #15699] Unified format for software tarballs
Date: Wed, 3 Nov 2021 13:33:33 -0400 (EDT)
User-agent: Lynx/2.8.9dev.16 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/1.0.2k

Follow-up Comment #12, task #15699 (project reproduce):

> in comment #1, you mentioned that ustar is the best tar format for
> futureproof-ness. But as far as I understood so far, tarlz works
> with the pax format. Won't that be an issue for longevity?

Pax is an extension on top of ustar. (Ustar is a subset of pax). What tarlz
does is to produce ustar archives by default (just like 'tar -Hustar'), but
tarlz adds one extended pax header for each member that requires it (for
example because the file name is too long for ustar). In the case of boost,
tarlz adds 46 extended pax headers in a total of 76801 members. AFAIK, this is
the most efficient and future proof that can be done just now.

You can use tarlz for all archives, and it will automatically add pax headers
only to those archives requiring them.

For more info see the "pax Interchange Format" section at
"The physical layout of the archive shall be identical to the ustar format".


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]