Date: Mon, 31 Aug 1998 12:10:40 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: Ralph Proctor <ralphgpr AT shadow DOT net>, Martin Str|mberg <ams AT ludd DOT luth DOT se>,
        djgpp AT delorie DOT com
Subject: Re: How to locate djgpp.env?
In-Reply-To: <Pine.A32.3.91.980831102630.35380D-100000@ieva06.lanet.lv>
Message-ID: <Pine.SUN.3.91.980831120708.22974O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 31 Aug 1998, Andris Pavenis wrote:

> Therefore I suggested to modify DJGPP.ENV to tell TAR not to use ramdrive.

This can only be done by the users, and then they should set TMPDIR in 
the environment.

DJGPP.ENV cannot handle this, since you have no idea what kind of drive 
is the one where %DJGPP% points.  It can be a CD-ROM, for example.

> However I'm afraid there are problems also with BASH when using pipes:
> 	some_cmd1 | some_cmd2
> perhaps will fail if output of some_cmd1 will not fit in drive specified
> with $TMPDIR. 

This can happen (and indeed happened to me), but only on very rare 
occasions.  One example is the shell script used in building TeX, which 
is why the README.djgpp file there says to make sure RAM disk is large 
enough.  Another case is when you build dictionaries for Ispell: the 
monstrous shell script that is run then produces 10MB of temorary files.