Message-Id: <199809020025.UAA07915@delorie.com>
Comments: Authenticated sender is <mert0407 AT sable DOT ox DOT ac DOT uk>
From: "George Foot" <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To: rjvdboon AT cs DOT vu DOT nl
Date: Tue, 1 Sep 1998 19:51:52 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re:  How to locate djgpp.env?
Reply-to: mert0407 AT sable DOT ox DOT ac DOT uk
CC: djgpp-workers AT delorie DOT com
Precedence: bulk

On  1 Sep 98 at 15:35, RJ vd Boon wrote:

> Maybe using something like:
> [tar]
> +TARTMP=%DJDIR%/tmp
> TMPDIR=%TARTMP%
> and a note in the README to set TARTMP to a local drive (NOT a
> ramdrive) if you are using a networked/CDROMed DJGPP (Yes, this is
> ugly, sorry.)

I'd suggest doing this the other way around:

    [tar]
    +TARTMP=%TMPDIR%
    TMPDIR=%TARTMP%

(if that's allowable in djgpp.env).  If it's done this way around,
people with ramdisks would need to change TARTMP if (and only if)
they're decompressing large archives, while people with DJGPP on
CD-ROM or a network drive don't need to change anything ever (so
long as TMPDIR is sensible).  If it's done the way you suggested, it
means that CD-ROM or networked DJGPP users need to change TARTMP or
they won't be able to use tar at all -- large archives or not -- and
in any case I think people who have set up a RAM disk are more likely
to be FAQ/README readers.  Mind you, since tar is a Unixy program its
users are probably going to read the READMEs anyway.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk
-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk