Bug#181632: acknowledged by developer (Re: Bug#181632: xserver-xfree86: could not open default font 'fixed')
On Thu, Feb 20, 2003 at 11:04:25AM -0500, Branden Robinson wrote:
> On Thu, Feb 20, 2003 at 11:42:08AM +0000, Luke Kenneth Casson Leighton wrote:
> > ... or is this the sort of thing that cannot be noted because
> > it's pre-install and the debconf system cannot do pre-install
> > "questions" like it can do pre-configure "questions"?
>
> Debconf scripts do not have a good way of knowing what is or is not
> going to be installed in the future. They can only check to see what is
> installed on the filesystem when they run, which might not have very
> much to do with what is installed a few minutes later.
(can the list of packages presently requested to be installed
be easily made available to the debconf scripts, such that
the packages both before and after batch installation may be
compared?)
> Note that
> debconf "preconfiguration" means this is the case quite frequently; all
> debconf questions are asked *before* packages are installed to the
> filesystem.
ah.
okay.
well it was worth a shot!
so the only viable option left is as part of a post-install
analysis, to put up a warning saying
"error, you have a package installed that is unlikely
to work! install one of the "recommended" packages
to make this package useable".
a bit like the advice from potato 2.2 from dselect which
said "pick a front-end; you can easily change the dselect
front-end at a later date"
... but in a similar fashion to this problem, that advice
didn't say _how_ you should "easily change the dselect
front-end in future"
:)
l.
Reply to: