X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;f=NEWS;h=31c2a6412ddb606f9070bb33b0a8c43a5efc93b1;hb=1063141801a96a5e65c678a8a4a2325e46d9cf97;hp=2538025b2eba2aa7d94a5a52832d33c7eeb89e3e;hpb=38d825f34b9220d3b68abd0405ff3b78346131c4;p=chaz%2Ftar diff --git a/NEWS b/NEWS index 2538025..31c2a64 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,100 @@ GNU tar NEWS - User visible changes. -Copyright 1994, 1995-1998, 1999 Free Software Foundation, Inc. +Copyright 1994-1999, 2000 Free Software Foundation, Inc. + +version 1.13.17 - Paul Eggert, 2000-01-07. + +* `tar --delete -f -' is no longer allowed; it was too buggy. +* Diagnostic messages have been made more regular and consistent. + +version 1.13.16 - Paul Eggert, 1999-12-13. + +* By default, tar now refuses to overwrite existing files when + extracting files from an archive; instead, it removes them before + extracting. There is one exception: existing nonempty directories + are not removed, nor are their ownerships or permissions extracted. + This fixes some longstanding security problems. + + The new --overwrite option enables the old default behavior. + + For regular files, tar implements this change by using the O_EXCL + option of `open' to ensure that it creates the file; if this fails, it + removes the file and tries again. This is similar to the behavior of + the --unlink-first option, but it is faster in the common case of + extracting a new directory. + +* By default, tar now ignores file names containing a component of `..' + when extracting, and warns about such file names when creating an archive. + To enable the old behavior, use the -P or --absolute-names option. + +* Tar now handles file names with multibyte encodings (e.g. UTF-8, Shift-JIS) + correctly. It relies on the mbrtowc function to handle multibytes. + +* The file generated by -g or --listed-incremental now uses a format + that is independent of locale, so that users need not worry about + locale when restoring a backup. This is needed for proper support + of multibyte characters. Old-format files can still be read, and + older versions of GNU tar can read new-format files, unless member + names have multibyte chars. + +* Many diagnostics have been changed slightly, so that file names are + now output unambiguously. File names in diagnostics now are either + `quoted like this' (in the default C locale) or are followed by + colon, newline, or space, depending on context. Unprintable + characters are escaped with a C-like backslash conventions. + Terminating characters (e.g. close-quote, colon, newline) + are also escaped as needed. + +* tar now ignores socket files when creating an archive. + Previously tar archived sockets as fifos, which caused problems. + +version 1.13.15 - Paul Eggert, 1999-12-03. + +* If a file's ctime changes when being archived, report an error. + Previously tar looked at mtime, which missed some errors. + +version 1.13.14 - Paul Eggert, 1999-11-07. + +* New translations ja, pt_BR. +* New options --help and --version for rmt. +* Ignore Solaris door files when creating an archive. + +version 1.13.13 - Paul Eggert, 1999-10-11. + +* Invalid headers in tar files now elicit errors, not just warnings. +* `tar --version' output conforms to the latest GNU coding standards. +* If you specify an invalid date, `tar' now substitutes (time_t) -1. +* `configure --with-dmalloc' is no longer available. + +version 1.13.12 - Paul Eggert, 1999-09-24. + +* `tar' now supports hard links to symbolic links. + +* New options --no-same-owner, --no-same-permissions. + +* --total now also outputs a human-readable size, and a throughput value. + +* `tar' now uses two's-complement base-256 when outputting header + values that are out of the range of the standard unsigned base-8 + format. This affects archive members with negative or huge time + stamps or uids, and archive members 8 GB or larger. The new tar + archives cannot be read by traditional tar, or by older versions of + GNU tar. Use the --old-archive option to revert to the old + behavior, which uses unportable representations for negative values, + and which rejects large files. + +* On 32-bit hosts, `tar' now assumes that an incoming time stamp T in + the range 2**31 <= T < 2**32 represents the negative time (T - + 2**32). This behavior is nonstandard and is not portable to 64-bit + time_t hosts, so `tar' issues a warning. + +* `tar' no longer gives up extracting immediately upon discovering + that an archive contains garbage at the end. It attempts to extract + as many files as possible from the good data before the garbage. + +* A read error now causes a nonzero exit status, not just a warning. + +* Some diagnostics have been reworded for consistency. + version 1.13.11 - Paul Eggert, 1999-08-23. @@ -16,7 +111,7 @@ version 1.13.11 - Paul Eggert, 1999-08-23. * For the --newer and --after-date options, the table of time zone abbreviations like `EST' has been updated to match current practice. Also, local time abbreviations are now recognized, even if they are - not in tar's hardwired table. Remember, thougy, that you should use + not in tar's hardwired table. Remember, though, that you should use numeric UTC offsets like `-0500' instead of abbreviations like `EST', as abbreviations are not standardized and are ambiguous. @@ -24,13 +119,9 @@ version 1.13.11 - Paul Eggert, 1999-08-23. version 1.13.10 - Paul Eggert, 1999-08-20. * `tar' now uses signed base-64 when outputting header values that are - out of the range of the standard unsigned base-8 format. This - affects archive members with negative time stamps or uids, and - archive members 8 GB or larger. The new tar archives cannot be read - by traditional tar, or by older versions of GNU tar. Use the - --old-archive option to revert to the old behavior, which uses - unportable representations for negative values, and which rejects - large files. + out of the range of the standard unsigned base-8 format. [This + change was superseded in 1.13.12, described above.] + version 1.13.9 - Paul Eggert, 1999-08-18.