[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: Tue, 2 Nov 2021 12:21:03 -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 #10, task #15699 (project reproduce):

> # If 'tar' fails with 'file name is too long (cannot be split)'
> # make the following change: '-Hustar' --> '-Hpax'.

The pax format has some inconvenients. It adds 1 KiB of headers per member,
which in the case of boost_1_77_0.tar increases the size from 744 MB to 822 MB
uncompressed. Half of those 78 extra MB are blocks of extended records not
protected by any checksum. See

Have you considered using tarlz to create the tarballs? It produces portable
archives with the minimum amount of pax headers required:

tarlz --solid --owner=root --group=root -9cf $name.tar.lz $name/

Tarlz can be found at


Reply to this item at:


  Message sent via Savannah

reply via email to

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