[task #15699] Unified format for software tarballs

[Antonio Diaz Diaz]

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
http://www.nongnu.org/lzip/manual/tarlz_manual.html#Amendments-to-pax-format

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 http://www.nongnu.org/lzip/tarlz.html


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?15699>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/