X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;f=README;h=6297ff162febb9c63d121e9182e1bbac8384e49e;hb=f3875c4a269a88121e5c1e72d3dc1a1fe545d2e8;hp=5970df8c70713b865ab808fac837895834536c7a;hpb=3698b9585bfe8a47ca39b9df9ae57db953b90393;p=chaz%2Ftar

diff --git a/README b/README
index 5970df8..6297ff1 100644
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
 README for GNU tar
 
-	Copyright 1990, 1991, 1992, 1994, 1997, 1998, 1999, 2000, 2001
-	Free Software Foundation, Inc.
+	Copyright (C) 1990, 1991, 1992, 1994, 1997, 1998, 1999, 2000,
+	2001, 2003 Free Software Foundation, Inc.
 
 	This file is part of GNU tar.
 
@@ -52,6 +52,10 @@ Besides those configure options documented in files `INSTALL' and
 operating system supports large files.  Typically, large files are
 those larger on 2 GB on a 32-bit host.
 
+The default archive format is GNU, this can be overridden by
+presetting DEFAULT_ARCHIVE_FORMAT while configuring. The allowed
+values are GNU, V7, OLDGNU and POSIX.
+
 The default archive device is now `stdin' on read and `stdout' on write.
 The installer can still override this by presetting `DEFAULT_ARCHIVE'
 in the environment before configuring (the behavior of `-[0-7]' or
@@ -60,14 +64,13 @@ in the environment before configuring (the behavior of `-[0-7]' or
 
 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.13 or later.  Install Perl, then Automake
-1.4 or later.  You might need Bison 1.28 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,
+and only then, Autoconf 2.57 or later.  Install Perl, then Automake
+1.7.5 or later.  Also, install gettext 0.12.1 or later.  You might
+need Bison 1.875 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>.  A bug report should contain
+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
 describe a solution, from which the problem might be uneasy to infer.
 If needed, submit actual data files with your report.  Small data files