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

Re: Configuration management, revision 3



Previously Jason Gunthorpe wrote:
> You are missing what he is saying. The current proposal is that we write
> basically a script to handle the configuration prompting. A script is
> probably necessary, but I think it probably should be in the post/pre inst
> not seperate..

preinst/postinst is way to late, since we want all questions asked before
we start physically unpacking the packages.

> For instance that current proposal does not seem to accomidate a master
> index of possible configuration values and their meanings and types, all
> we have a query language. [Envision downloading configuation.gz, firing
> up your LDAP manipulator and configuring your machine -before installing-]

I have to admint that would be utter coolness.

> Value: foo/configd
> Type: boolean
> Private: yes
> Description: Controls some strange internal thing
> 
> Which is ultimately more usefull?

But you loose something there: the ability to decide if a question should
be ask, unless you implement a dependency scheme. The menuconfig of the
kernel already does that, but in a very simple way. 
 
> Personally I think the use of the query language as I understood it is not
> what we -really- want, it serves the purpose of communicating (and
> controlling!) the query process. What we want is a way to get/set values
> out of the database, I've been thinking about something like this [excuse
> my shell]
 
You're loosing me here. If you have something like dpkg-var to access
the data, this is the already there? The reason the frontend also
accesses the database is to make easy to switch to a non-interactive frontend
without changing a configmodule.

> The other 'missing' fragment is what to do if the user changes a database
> entry once the package is installed. It is important to leave that
> possiblity open so in future we can have 'push' configuration.

So you want the ability to add a trigger? You attach a trigger to a part
of the database, and when the part is changed the trigger is triggered
and gets to do something, like reconfigure a package?

Wichert.

-- 
==============================================================================
This combination of bytes forms a message written to you by Wichert Akkerman.
E-Mail: wakkerma@wi.LeidenUniv.nl
WWW: http://www.wi.leidenuniv.nl/~wichert/

Attachment: pgpw6qZqT8ea7.pgp
Description: PGP signature


Reply to: