./archivers/gtar-base, The GNU tape archiver with remote magnetic tape support

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 1.29, Package name: gtar-base-1.29, Maintainer: pkgsrc-users

GNU tar, originally shipped as NetBSD's "tar" up to version 1.3, is a
full-featured tar command that can access remote and local magnetic tapes,
tar files (ustar, POSIX, and V7), and even compressed or gzipped versions
of these. Note that as of the current version of GNU tar (1.12), gtar
does not create "correct" ustar archives.

Master sites: (Expand)

SHA1: 057977c86293fddcbb04075ca70f41079e044949
RMD160: 27a18fd2a557fb6dc37218c96b3c3223527604a4
Filesize: 2652.337 KB

Version history: (Expand)

CVS history: (Expand)

   2016-05-31 17:04:51 by Makoto Fujiwara | Files touched by this commit (6) | Package updated
Log message:
- two patches are removed, upstream change
- Updated archivers/gtar      to 1.29
  Updated archivers/gtar-base to 1.29
  Updated archivers/gtar-info to 1.29
version 1.29 - Sergey Poznyakoff, 2016-05-16

* New options: --verbatim-files-from, --no-verbatim-files-from

The --verbatim-files-from option instructs tar to treat each line read
from a file list as a file name, even if it starts with a dash.

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.

Use the --verbatim-files-from option to disable this special handling.
This facilitates the use of tar with file lists created automatically
(e.g. by find(1) command).

This option affects all --files-from options that occur after it in
the command line.  Its effect is reverted by the
--no-verbatim-files-from option.

* --null option reads file names verbatim

The --null option implies --verbatim-files-from.  I.e. each line
read from null-delimited file lists is treated as a file name.

This restores the documented behavior, which was broken in version

* 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:


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

See <https://wiki.debian.org/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

     Use lseek(2) SEEK_DATA and SEEK_HOLE "whence" parameters.

     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.
   2016-02-25 10:28:37 by Jonathan Perkin | Files touched by this commit (9)
Log message:
   2015-11-03 01:56:27 by Alistair G. Crooks | Files touched by this commit (93)
Log message:
Add SHA512 digests for distfiles for archivers category

Problems found with existing distfile for eagle:
No changes made to these distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2015-05-03 16:32:12 by Sevan Janiyan | Files touched by this commit (1)
Log message:
Force the use of the gnulib version of wctype.h, bundled with gtar, when building
on AIX. This is a workaround for an issue where though the wctype.h included on
system was found, wctype_t & wctrans_t were deemed unsuitable, causing the build
to fail due to previous declaration with confliciting types.

Reviewed by wiz@
   2015-04-23 11:15:19 by Sevan Janiyan | Files touched by this commit (1)
Log message:
rmt is not built on AIX
Exclude AIX from PLIST.rmt

Reviewed by wiz@
   2015-04-19 16:31:06 by Tobias Nygren | Files touched by this commit (1)
Log message:
Does not need USE_FEATURES=snprintf.
snprintf is provided internally by gnulib.
   2015-01-26 13:41:53 by Jonathan Perkin | Files touched by this commit (2)
Log message:
Add credit to Fink for the diagnosis and suggested fix.
   2015-01-26 13:30:30 by Jonathan Perkin | Files touched by this commit (3) | Package updated
Log message:
Do not call into gettext which may not be async-signal-safe in between fork
and exec.  Fixes crashes on OSX when LC_ALL is unset.