[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debconf/frontend versus DEBIAN_FRONTEND

On Wed, Sep 22, 2004 at 09:20:14PM +0200, Jö Fahlke wrote:
> Am Mi, 22. Sep 2004, 18:59:02 +0200 schrieb Jö Fahlke:
> > My plan is to not automagically set any variables if the corresponding
> > debconf option is set in the database.  Since these variables are set
> > from scripts in run-parts-style directories it's probably easiest to
> > use a seperate skript which tests if a single debconf option is set.
> > Is that kind of skript already available?
> Patch for DEBCONF_FRONTEND is attached.
> I'ts totally untested at the moment since my I don't want to test it
> on my work machine and the sparc box is not installed, so I can't
> build d-i there.
> I had to create debconf-fget in packages/debian-installer/utils,
> shamelessly copying from debconf-get.

debconf/frontend doesn't have a default, so I'd be inclined to just
debconf-get it and see if it's non-empty. Testing the 'seen' flag seems
a bit weird since it hasn't in fact been shown to the user.

Colin Watson                                       [cjwatson@debian.org]

Reply to: