Date:	Wed, 7 Mar 2001 09:23:47 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Fetish.pm band-aid (Fileutils testsuite)
In-Reply-To:	<3AA55AC9.B6A954A1@phekda.freeserve.co.uk>
Message-ID:	<Pine.SUN.3.91.1010307092328.20641D-100000@is>
MIME-Version:	1.0
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

On Tue, 6 Mar 2001, Richard Dawe wrote:

> Tim Van Holder wrote:
> > Actually, since newer autoconfs also require such a full path, you
> > should consider putting
> > 
> >         SHELL=/dev/env/DJDIR/bin/bash.exe (or sh.exe)
> > 
> > in your config.site.
> 
> That sounds like a good idea, but I'd like to keep my DJGPP set up as
> close to "standard" as possible, so that I don't miss (more) things when
> I'm porting/building packages.
> 
> Will the DJGPP port of autoconf 2.50 ship with config.site?

I think you should put a config.site file in the distribution of the
port, and arrange for the configure script to point $CONFIG_SITE at
it.  It is IMHO unsafe to rely on last-minute changes in the
system-wide config.site, even if the next Autoconf or Bash port solves
this, since users might have old ports on their machines.

Many DJGPP ports come with config.site files in their source
distributions, because at the time they were ported config.site was
absent from the Bash distribution.  So this is a proven solution.

- Raw text -