[Dbconfig-common-devel] Any advice on preseeding the initial dbconfig-install/dbconfig-upgrade/dbconfig-remove prompts ?

[sean finney]

hi roelf,

i'm going to re-forward this to the dbconfig mailing list, for the sake of 
posterity.

On Thursday 21 June 2007 00:33:10 Roelf Diedericks wrote:
> Hi Sean.
>
> I managed to get things going by doing a db_set dbconfig-common/install
> and package/install in the
> postinst/config scripts.
>
> The application is a custom debian based appliance with openradius, that
> requires a pretty seamless
> unprompted installation/upgrade through a web interface.

okay, good to know that works.  for the record i don't promise that i won't 
move around template names/locations/usage (i.e. i don't consider it part of 
the "exported api").  however, i won't go out of my way to break it, and even 
if i *do* change this, it should still be possible to use the same 
technique/concept.

also, given that this is for a private (i.e. non debian main archive) 
package/system, i think that makes perfect sense.


	sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20070621/318b8a16/attachment.pgp