Re: Problems with using debconf in init script...
- To: email@example.com
- Subject: Re: Problems with using debconf in init script...
- From: Mark Brown <firstname.lastname@example.org>
- Date: Thu, 1 Feb 2001 10:34:35 +0000
- Message-id: <20010201103435.H821@tardis.ed.ac.uk>
- Mail-followup-to: Mark Brown <email@example.com>, firstname.lastname@example.org
- In-reply-to: <email@example.com>; from firstname.lastname@example.org on Wed, Jan 31, 2001 at 04:52:59PM -0800
- References: <20010130113618.F20791@azure.humbug.org.au> <email@example.com> <20010130121243.H20791@azure.humbug.org.au> <firstname.lastname@example.org> <20010130003135.S2501@alcor.net> <email@example.com> <20010130024534.W2501@alcor.net> <firstname.lastname@example.org> <20010131122544.C13069@tardis.ed.ac.uk> <email@example.com>
On Wed, Jan 31, 2001 at 04:52:59PM -0800, Philippe Troin wrote:
> Mark Brown <firstname.lastname@example.org> writes:
> > One potential problem would be if the config script was being run on
> > a different system to that which was being configured.
> How would you do that though ? Is there a standard way of
> "preconfiguring" packages on a different host (other than copying the
> debconf databases and templates) ?
I don't think there's any backends that do it at the moment but it was
one of the considerations when debconf was being designed.
Mark Brown mailto:email@example.com (Trying to avoid grumpiness)
Description: PGP signature