A database driven aproach could be one of the more flexible. I am thinking
on a database structure like:

package{version}|question-string|answer

(version is optional)

This could be easily handled with expect (thank's for the mail, Henry!).
The algorithm could be:

1. Get package name from: "Configuring package ..."
2. Look for question strings for package (if they are any)
3. If lookup matches, then give the answer to the script
4. repeat for next package until finished

pro: easily configurable, very flexible if matching strings use regexp, no
change to dpkg required, could also automate other steps of Henry's
configuration

con: tcl, expect and related libraries required, no support for dselect,
could be a overkill


Bye,
Hubert


------------------------------------------------------------------------------
Hubert Weikert   DB1MQ   Member of DARC (www.darc.de) and FITUG (www.fitug.de)
Email: [EMAIL PROTECTED]    [EMAIL PROTECTED]    http://www.cube.net/~weikert/
Book: Kryptographie mit dem Computer (PGP Praxis) ISBN 3-7905-1503-5  DM 19,80
Key = 21978C61  fingerprint = 99 38 A5 83 C8 76 F4 E1  A7 9C B9 70 9A A7 70 10


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to