Sender: richdawe AT bigfoot DOT com
Message-ID: <3741BC50.A4B8D51D@bigfoot.com>
Date: Tue, 18 May 1999 20:15:28 +0100
From: Richard Dawe <richdawe AT bigfoot DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.1 i586)
MIME-Version: 1.0
To: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: DSM/scripting spec, version 0.1
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990516134714 DOT 26252R-100000 AT is> <37405136 DOT E7E8D79C AT inti DOT gov DOT ar>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

salvador wrote:
> BTW: What language will support the pre/post-install scripts? in Debian
> they could be bash and/or Perl scripts. Yeap: Perl and bash are part of
> an special package called Debian-base, so any Debian system have at
> least it installed ...

I was intending to make it support any language, i.e. by checking for the
shebang (#!) notation or, failing that, the file extension.

I was intending to write the installer to check all the 'requires' fields
before installing. So, if the install script required Perl, you'd put it
in as a 'requires'. The problem I can forsee with this is if you have a
non-DJGPP package version of Perl, e.g. ActivePerl for Win32 (*), in which
case the dependency will fail. Maybe it would be better just to see if
'perl' is anywhere in the path. Perhaps a configuration file could be used
to override the locations of binaries like Perl.

(*) See http://www.activestate.com

Is there any consensus on storing configuration files in $DJDIR/etc? In my
experience with DJGPP so far the configuration files have either been in
$HOME or some other directory specified by environment variable.