Date: Sun, 13 May 2001 15:57:23 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: djgpp-workers AT delorie DOT com, JT Williams <jeffw AT darwin DOT sfbr DOT org>
Subject: Re: DJGPP 2.04 release date
In-Reply-To: <20010513145204.A379@lauras.lt>
Message-ID: <Pine.SUN.3.91.1010513155522.15149A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 13 May 2001, Laurynas Biveinis wrote:

> > I usually unpack the original .tar.gz file under LFN=n (or plain DOS), 
> > and then use the tarchange.lst file as the starting point.  A few Sed 
> > runs is all you need to get an alias list.
> 
> I don't have my semifinished alias list right here, right now, but
> I recall that there was little possible automation.

This is a misunderstanding: tarchange.lst is always created when djtar 
cannot unpack the the archive without conflicts.  The mapping of the 
problematic files is something you need to supply yourself; I didn't mean 
to say that I have some magic which does that automatically.