Date: Mon, 3 Apr 2000 10:51:06 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Bash 2.04 beta 1 now available
In-Reply-To: <38E71B1E.17249.B912B@localhost>
Message-ID: <Pine.SUN.3.91.1000403104804.26246D-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, 2 Apr 2000, Mark E. wrote:

> > On Sat, 25 Mar 2000, Mark E. wrote:
> > 
> > > Bash 2.04 beta 1 is now available from 
> > > "http://members.xoom.com/snowball3/djgpp/". The biggest user-visible change
> > > is that the variables PATH_EXPAND, SYSROOT, and PATH_SLASH no longer have
> > > any special meaning.
> 
> In Bash 2.03, PATH_EXPAND=y would change '/dev/c/' style paths to 'c:' style 
> paths. Bash 2.04 no longer does this.

Is that really a good idea?  This could break non-DJGPP programs and 
DJGPP programs compiled with old versions of libc.

What are the reasons for dropping PATH_EXPAND, anyway?  After all, if 
someone doesn't want it, they can simply avoid using it.

And what about PATH_SLASH?

As for SYSROOT, I have no problems with dropping it: I think it was evil 
in the first place.