Sender: richdawe AT bigfoot DOT com
Message-ID: <373DE0DA.A8D2E50C@bigfoot.com>
Date: Sat, 15 May 1999 22:02:19 +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 AT delorie DOT com
Subject: Re: DSM/scripting spec, version 0.1
References: <373CC051 DOT C3E1F919 AT meridian22 DOT net> <199905151653 DOT MAA22552 AT envy DOT delorie DOT com> <373DB8AE DOT E0C10002 AT softhome DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Laurynas Biveinis wrote:
> 
> > Security alert: the user should have the options of (1) not running
> > the scripts, or (2) seeing them before running them.
> 
> Is it OK to run silently under LBInstDJ? A newbie who will use LBInstDJ
> will not understand those scripts if they are complex and he will get
> them from trusted source - simtel. However, above is true for
> installing some other zips with zippo.

How many packages are really going to require scripts anyhow? Given that
most packages don't require any scripts to be run at moment, I guess we
good leave this out. Maybe it would be better to provide a README file to
be displayed after installation? If any scripts needed to be run, they
would be detailed in this file. The user would then have control.

With regard to the README file, we need another new field:

install-readme: [File name]

Given that zippo will extract the DSM before proceeding, it could also
extract the readme.:

zippo -q -p <package zip> --install-readme

(Query package <...> and display readme).

Interfacing between LBInstDJ and zippo should be controlled be return
codes.