X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs Date: Mon, 28 Feb 2000 13:16:53 +0100 (MET) From: Hans-Bernhard Broeker X-Sender: broeker AT acp3bf To: djgpp-workers AT delorie DOT com Subject: Re: ANNOUNCE: Bison 1.28 ported to DJGPP In-Reply-To: Message-ID: 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 Sun, 27 Feb 2000, Eli Zaretskii wrote: > > On Fri, 25 Feb 2000, Hans-Bernhard Broeker wrote: > > > This is one point where the design limitations of djgpp.env show through: > > a package cannot automatically modify its own djgpp.env sections, > > selectively, without the risk of breaking the user's own personalizations. > > If you have suggestions to improve this, please tell what they are. Not really. I haven't looked into the 'installer' programs that others have been writing for DJGPP. That would have to be the place for this kind of things to be implemented. The limitation that exists is the fact that currently DJGPP installation packages are really just .zip files, and that there is no tool on whose presence we could rely on every user's system to carry out file modifications from the automatic execution .bat file you can (!) store in a .zip file. The installer would need a kind of 'sed' script interpreter built into it to automatically carry out the modifications. A builtin 'patch' wouldn't work, as it requires knowledge about the previous state, which isn't available reliably. Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.