Re: Problems with using debconf in init script...
- To: debian-devel@lists.debian.org
- Subject: Re: Problems with using debconf in init script...
- From: Mark Brown <broonie@sirena.org.uk>
- Date: Thu, 1 Feb 2001 10:34:35 +0000
- Message-id: <[🔎] 20010201103435.H821@tardis.ed.ac.uk>
- Mail-followup-to: Mark Brown <broonie@sirena.org.uk>, debian-devel@lists.debian.org
- In-reply-to: <87elxjusus.fsf@ceramic.fifi.org>; from phil@fifi.org on Wed, Jan 31, 2001 at 04:52:59PM -0800
- References: <20010130113618.F20791@azure.humbug.org.au> <87wvbdhl57.fsf@ceramic.fifi.org> <20010130121243.H20791@azure.humbug.org.au> <87snm1hdzq.fsf@ceramic.fifi.org> <20010130003135.S2501@alcor.net> <87lmrto75j.fsf@ceramic.fifi.org> <20010130024534.W2501@alcor.net> <87d7d4bsjz.fsf@ceramic.fifi.org> <20010131122544.C13069@tardis.ed.ac.uk> <87elxjusus.fsf@ceramic.fifi.org>
On Wed, Jan 31, 2001 at 04:52:59PM -0800, Philippe Troin wrote:
> Mark Brown <broonie@sirena.org.uk> 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:broonie@tardis.ed.ac.uk (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFS http://www.eusa.ed.ac.uk/societies/filmsoc/
Attachment:
pgp3YUlw0W4ue.pgp
Description: PGP signature
Reply to: