pkgsrc/archivers/gtar-base/distinfo

12 lines
745 B
Text
Raw Normal View History

$NetBSD: distinfo,v 1.44 2019/05/02 20:27:42 wiedi Exp $
SHA1 (tar-1.32.tar.bz2) = d0b0259689062d7700480f74c547f62f18e7412d
RMD160 (tar-1.32.tar.bz2) = b83c063c4eea4f36bf70c6be67a1c7fc74e5e82f
SHA512 (tar-1.32.tar.bz2) = 3139e87112123269ee0600243b3ea081687cc93667bef5832bfe3c785c1be622f520f00fcfbdf44ad1d3247866d0ecfe347a85bbfec38eb38fa1014baef566f6
Size (tar-1.32.tar.bz2) = 2947264 bytes
SHA1 (patch-Makefile.in) = 78cc142b9370317c52215c106ea1e7217e71f9b5
(pkgsrc) - two patches are removed, upstream change (upstream) - 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 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: 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> 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.
2016-05-31 17:04:51 +02:00
SHA1 (patch-gnu_readlinkat.c) = ce9869bfcd75005bb4ddac4e3223df01a26a2b29
SHA1 (patch-gnu_sys-limits.h) = b644d4f7915cac5757cb197966ec5f37553f3237
SHA1 (patch-lib_xattr-at.c) = c69631c118558c0c056feb5b55188b2b4c92cc19
SHA1 (patch-src_system.c) = cd9f7358fa93ed0ba4a1b3fffdae5d7f84ef4791