Sender: rich AT delorie DOT com Message-ID: <38BAD0D4.54CE29B0@bigfoot.com> Date: Mon, 28 Feb 2000 19:47:32 +0000 From: Richard Dawe X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586) X-Accept-Language: de,fr MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: ANNOUNCE: Bison 1.28 ported to DJGPP References: <38BA7CD5 DOT F4268EAA AT softhome DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hello. [BCC'd to zippo-workers AT onelist DOT com] Laurynas Biveinis wrote: > > Hans-Bernhard Broeker wrote: > > 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. > > Yes. > > > 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. > > Zippo, once finished, should be common on every system. Since it will > have some built-in scripting capability, it is OK for this task. In fact, I have the intention of adding support for external scripting languages too, e.g. spawning bash to modify DJGPP.ENV would be quite easy. The DJGPP Software Manifest (DSM) for the package would have a dependency on bash (whatever version), so that the user cannot install the package until bash has been installed. I don't really intend zippo's built-in scripting to be a heavy-duty scripting language, more something for displaying things like "Now read readme.txt" or "Don't forget to add the Emacs bin directory to your path". I'd rather re-use bash's scripting power than reinvent the wheel. Bye, -- Richard Dawe richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/