Date:	Wed, 11 Apr 2001 12:31:28 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT ZAHAV DOT NET DOT IL
To:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
Message-Id:	<3791-Wed11Apr2001123128+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<CAEGKOHJKAAFPKOCLHDIIEFECCAA.tim.van.holder@pandora.be>
Subject:	Re: New bash 2.04 beta release
References:	<CAEGKOHJKAAFPKOCLHDIIEFECCAA DOT tim DOT van DOT holder AT pandora DOT be>
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

> From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
> Date: Tue, 10 Apr 2001 20:24:44 +0200
> 
> Using ';' on DOS is more natural anyway, and autoconf can be used to
> propagate the correct pathsep to the necessary files (for example, my
> local ld tree has a genscripts.in file that autoconf transforms to
> genscripts.sh, so it uses ';' instead of ':' where appropriate).

The problem is, the path separator issue is not limited to Autoconf
and the scripts it generates.  It is also relevant to running shell
scripts which have nothing to do with Autoconf.  If PATH_SEPARATOR is
not set to :, these scripts will break.

Is it possible to modify Autoconf to use a different variable for this
purpose?  It would be nice if we could continue to use PATH_SEPARATOR
without risking the conflict with Autoconf.

- Raw text -