-Here is GNU `tar' 1.12. Please glance through *all* sections of this
+Please glance through *all* sections of this
`README' file before starting configuration. Also make sure you read files
`ABOUT-NLS' and `INSTALL' if you are not familiar with them already.
-If you got the `tar' distribution in `shar' format, timestamps ought to be
-properly restored, do not ignore such complaints at `unshar' time.
+If you got the `tar' distribution in `shar' format, time stamps ought to be
+properly restored; do not ignore such complaints at `unshar' time.
GNU `tar' saves many files together into a single tape or disk
archive, and can restore individual files from the archive. It includes
Besides those configure options documented in files `INSTALL' and
`ABOUT-NLS', a few extra options may be accepted after `./configure':
-* `--with-included-malloc' or `--without-included-malloc' may override
-the automatic choice made by `configure' about using included GNU malloc.
-
* `--with-dmalloc' is a debugging option for looking at memory management
problems, it prerequires Gray Watson's package, which is available as
`ftp://ftp.letters.com/src/dmalloc/dmalloc.tar.gz'.
For comprehensive modifications to GNU tar, you might need tools beyond
those used in simple installations. Fully install GNU m4 1.4 first,
-and only then, Autoconf 2.12 with officious patches held in `AC-PATCHES'.
-Install Perl, then Automake 1.1n with officious patches in `AM-PATCHES'.
-You might need Bison 1.25 with officious patches in `BI-PATCHES' (but yacc
-and byacc may be OK for you), and GNU tar itself. All are available on
-GNU archive sites, like in ftp://prep.ai.mit.edu/pub/gnu/, but Automake
-is still ftp://ftp.cygnus.com/pub/tromey/automake-1.1n.tar.gz.
-
-Send bug reports to `tar-bugs@gnu.ai.mit.edu'. (Beware, old-timers: it is
+and only then, Autoconf 2.13 or later. Install Perl, then Automake
+1.4 or later. You might need Bison 1.26 or later, and GNU tar itself.
+All are available on GNU archive sites, like in
+ftp://ftp.gnu.org/pub/gnu/.
+
+Send bug reports to `bug-tar@gnu.org'. (Beware, old-timers: it is
`@gnu', not `@prep'; and not `bug-gnu-utils' anymore.) A bug report is
an adequate description of the problem: your input, what you expected,
what you got, and why this is wrong. Diffs are welcome, but they only
* Failed `incremen.sh'.
-In an NFS environment, lack of synchronisation between machine clocks
-might create difficulties to any tool comparing dates and file timestamps,
+In an NFS environment, lack of synchronization between machine clocks
+might create difficulties to any tool comparing dates and file time stamps,
like `tar' in incremental dumps. This has been a recurrent problem in
GNU Makefiles for the last few years. We would like a general solution.
* File attributes.
About *security*, it is probable that future releases of `tar' will have
-some behaviour changed. There are many pending suggestions to choose from.
+some behavior changed. There are many pending suggestions to choose from.
Today, extracting an archive not being `root', `tar' will restore suid/sgid
bits on files but owned by the extracting user. `root' automatically gets
-a lot of special priviledges, `-p' might later become required to get them.
+a lot of special privileges, `-p' might later become required to get them.
GNU `tar' does not properly restore symlink attributes. Various systems
-implement flavours of symbolic links showing different behaviour and
+implement flavors of symbolic links showing different behavior and
properties. We did not successfully sorted all these out yet. Currently,
the `lchown' call will be used if available, but that's all.
execution or usability bugs. This was accompanied all over with an
internal cleanup in the sources, and the reassembly of a `tar' manual.
-The `BACKLOG' file shows an approximative priorisation of the many pending
+The `BACKLOG' file shows approximate priorities of the many pending
problems and suggestions. Besides pending problems and all other matters
listed above, the cleanup is planned to continue and extend to the general
-organisation of the code, preparing a long time in advance for a possible
+organization of the code, preparing a long time in advance for a possible
merge of the `cpio' and `tar' distributions, into some common `paxutils'.
We also want to address some long-awaited performance issues (for example:
double buffering) or enhancements (for example: per-file compression).
projects / chaz / tar / blobdiff