Date: Mon, 28 Feb 2000 17:21:12 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: djgpp-workers AT delorie DOT com, Zippo Workers <zippo-workers AT onelist DOT com>
Subject: Re: ANNOUNCE: Bison 1.28 ported to DJGPP
In-Reply-To: <38BA7CD5.F4268EAA@softhome.net>
Message-ID: <Pine.SUN.3.91.1000228171916.13170D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 28 Feb 2000, Laurynas Biveinis wrote:

> I suggest do it as follows: each package provides its own part of
> configuration file, and on every installation/deinstallation the
> main djgpp.env should be concatenated from all those parts.

Somebody suggested in the past a better solution: support for 
program-specific .env files.  That is, the startup code of a program 
foo.exe would look for a file foo.env *after* reading djgpp.env.

Volunteers are welcome to send in patches ;-).