Message-Id: <199701192041.VAA07597@math.amu.edu.pl>
Comments: Authenticated sender is <grendel AT ananke DOT amu DOT edu DOT pl>
From: "Mark Habersack" <grendel AT ananke DOT amu DOT edu DOT pl>
Organization: What? (Poznan, Poland)
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Sun, 19 Jan 1997 21:55:12 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Configure scripts
Reply-to: grendel AT ananke DOT amu DOT edu DOT pl

Once upon a time (on 19 Jan 97 at 17:54) Eli Zaretskii said:

> Since the port of `bash' can run configure scripts almost unchanged, I
> wonder if it is appropriate to base DJGPP source distributions on the
> assumption that people who build from sources have `bash' and the
> necessary XXX-utils installed.  It certainly makes the porting a lot
Hmm... The perspective is certainly tempting, but it is hard to assum, IMHO,
that everyone has bash/tools on their disks. OTOH, I think that those 
interested in recompiling/modifying sources do have the tools. 

> easier (I estimate that as much as 30% of the work goes into tweaking
> Makefile.in into DOS-compatible Makefile, especially since it diverts 
> energy from the *real* job). 
Wouldn't it be possible to pre-generate config scripts with bash on your machine and 
distribute them along with the sources? That way you have all the birds in 
your hand: someone who doesn't have bash/tools already has a pre-configured 
package and someone else with bash/tools can reconfigure it at will. Or is 
that solution not flexible enough?