Re: Problems with using debconf in init script...
Matt Zimmerman <email@example.com> writes:
> On Thu, Feb 01, 2001 at 02:21:55PM -0800, Philippe Troin wrote:
> > Mark Brown <firstname.lastname@example.org> writes:
> > > On Wed, Jan 31, 2001 at 04:52:59PM -0800, Philippe Troin wrote:
> > > > Mark Brown <email@example.com> 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.
> > Ok. It's wise then to avoid writing to the filesystem in a debconf
> > config script.
> Why only writing? Consider the case where the system running the
> configure script has a non-modified config file (causing the
> question to be skipped), but the remote system does not.
Then we're screwed. Well, I can recheck in the postinst...
Do you have a solution ?