Date: Tue, 30 Mar 1999 16:56:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Jeff Williams <jeffw AT darwin DOT sfbr DOT org>
cc: djgpp AT delorie DOT com
Subject: Re: tarchange.lst
In-Reply-To: <199903301409.IAA09201@darwin.sfbr.org>
Message-ID: <Pine.SUN.3.91.990330165338.6660E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 30 Mar 1999, Jeff Williams wrote:

> What is the purpose of the file `tarchange.lst'?  I sometimes find a
> leftover, zero-length file by this name after working with djtar.
> E.g., try `djtar --help'.  It appears from the sources (main of djtar.c
> is the only place I find the string `tarchange') that tarchange is
> supposed to contain ``changes'', but *what* changes?

The file records changes of file names.  When DJTAR cannot create a new
file, either because a file by that name already exists, or because the
file's name is invalid for the underlying OS, it prompts you for another
name.  All the changes are stored in DJTAR's internal data structure, and
the conversions are written out when the program exits.  This is a
feature:  it documents the changes of the original file names, and can be
used the next time by submitting the tarchange.lst file to DJTAR (see the
-n switch). 

It might be a good idea not to leave an empty file behind, though.