Date: Wed, 5 Feb 1997 17:33:29 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
cc: "John M. Aldrich" <fighteer AT cs DOT com>,
        Gurunandan R Bhat <grbhat AT unigoa DOT ernet DOT in>, djgpp AT delorie DOT com
Subject: Re: tar for DJGPP | Followup:
In-Reply-To: <Pine.GSO.3.95.970204235001.21899F-100000@sparkie.gnofn.org>
Message-ID: <Pine.SUN.3.91.970205172821.2719H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 4 Feb 1997, Colin W. Glenn wrote:

> > I think you've caused a lot of trouble by redirecting both stdout and 
> > stderr to the same file, when there's no need for this.
> 
> I'm a neat freak, I like my programs to _behave_, especially concerning

What's misbehaving about putting stderr and stdout to two different files?

> > None.  Do you really want your precious sources to be quitely dumped to 
> > Kingdom Come?
> 
> I'm not sure I follow, how so?

DJTAR was created to handle Unix-born tar files.  Those tar files include
files whose filenames are illegal on MSDOS, or clash with one another
within the restricted 8+3 DOS namespace.  When a clash happens which DJTAR
cannot resolve by itself, it prints a message and asks what to do.  Making
DJTAR shut up would prevent you from knowing that something went wrong, so
you wind up with some of the files from the tar file missing.  Quietly.