[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Simple solution to pre-installation configuration



On Mon, 27 Jan 1997, Christoph wrote:

> On Tue, 28 Jan 1997, Richard G. Roberto wrote:
> 
> richr >> My example configure script with the adpkg package already reads
> richr >> /var/lib/config/packagename and then asks the user for changes. Is that
> richr >> what you are looking for? A reconfiguration is simply another
> richr >> configuration.
> richr >
> richr >Well, yeah, I guess.  But ultimately, there should be a way to
> richr >tell adpkg wich you prefer up front (i.e. "don't ask, just take
> richr >defaults for missing values", "replace current config with new
> richr >default", etc.).  Sort of a configure profile so that perhaps a
> richr >command line switch can change this behavior (or an environment
> richr >variable?).  I'll take a look at adpkg, maybe this is already the
> richr >case.
> 
> The "dont ask" policy means simply not running the configure script. The
> package notes that no /var/lib/config/package exists and assumes defaults.
> 
> Other behavior could be standardized with a command line parameter to 
> the configure script.
> 
> --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
> Please always CC me when replying to posts on mailing lists.
> 

Isn't be good to add a --quiet or --no-prompt to ours policy script 
options? This will disable mostly all prompt (including the wait for 
return after a message) and assume default value or later configuration 
for all package. 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com


Reply to: