newsGNU tar - News: tar 1.29

 
 
Latest News
Version 1.34 posted by gray, Sat 13 Feb 2021 11:53:17 AM UTC - 0 replies
Version 1.33 posted by gray, Thu 07 Jan 2021 03:05:59 PM UTC - 0 replies
Version 1.32 posted by gray, Sat 23 Feb 2019 01:15:56 PM UTC - 0 replies
Version 1.31 posted by gray, Wed 02 Jan 2019 07:17:56 PM UTC - 0 replies
Version 1.30 posted by gray, Sun 17 Dec 2017 12:24:33 PM UTC - 0 replies
[Submit News]
[26 news in archive]

tar 1.29

Item posted by Sergey Poznyakoff <gray> on Mon 16 May 2016 07:20:04 PM UTC.

GNU tar version 1.29 is available for download.

New in this release:



File lists are supplied with the *--files-from* (*-T*) option.  By default, each line read from a file list is first stripped off the leading and trailing whitespace and, if the result begins with a dash, it is treated as tar command line option.

(e.g. by *find*(1) command).


== --null option reads file names verbatim ==


This restores the documented behavior, which was broken in version 1.27.

== New options: --owner-map=FILE and --group-map=FILE ==

These two options provide fine-grained control over what user/group names (or IDs) should be mapped when adding files to archive.

For both options, _FILE_ is a plain text file with user or group mappings.  Empty lines are ignored.  Comments are introduced with *#* sign (unless quoted) and extend to the end of the corresponding line.  Each non-empty line defines translation for a single UID (GID).  It must consist of two fields, delimited by any amount of whitespace:

+verbatim+
     OLDNAME NEWNAME[:NEWID]


_OLDNAME_ is either a valid user (group) name or a ID prefixed with *+*.  Unless _NEWID_ is supplied, _NEWNAME_ must also be either a valid name or a
_*+*ID_.  Otherwise, both _NEWNAME_ and _NEWID_ need not be listed in the system user database.

== New option --clamp-mtime ==

The new *--clamp-mtime* option changes the behavior of *--mtime* to only use the time specified if the file mtime is newer than the given time.
The *--clamp-mtime* option can only be used together with *--mtime*.

Typical use case is to make builds reproducible: to loose less information, it's better to keep the original date of an archive, except for files modified during the build process. In that case, using reference (and thus reproducible) timestamps for the latter is good enough.

See [https://wiki.debian.org/ReproducibleBuilds ReproducibleBuilds], for more information.

== Deprecated --preserve option removed ==

== Sparse file detection ==

Tar now uses *SEEK_DATA*/*SEEK_HOLE* on systems that support it.  This allows for considerable speed-up in sparse-file detection.

New option *--hole-detection* is provided, that allows the user to select the algorithm used for hole detection.  Available arguments
are:

=== --hole-detection=seek ===

Use *lseek*(2) *SEEK_DATA* and *SEEK_HOLE* _whence_ parameters.

=== --hole-detection=raw ===

Scan entire file before storing it to determine where holes are located.

The default is to use *seek* whenever possible, and fall back to *raw* otherwise.




No messages in tar 1.29

 

Back to the top


Powered by Savane 3.9