Bug#214916: Debconf question for configuring modules is hard to answer
Hi Enrico,
On Thu, 9 Oct 2003, Enrico Zini wrote:
> Here is a list of problems I've found:
>
> - Module names have no description
They have a descrition but it is not shown. The main issue is that the
descriptions are very long and they do not fit in few chars.
> - There are too many modules to choose to remember what they are, and
> too many to look up documentation
This is absolutely nothing i can do about. apache ships modules and there
tons of others that are external and that will appear in that list.
> - It does not tell where the defaults have been taken from: is it from
> my existing apache configuration or are they the defaults that come
> in the Debian package? In the first case, I'd want to just hit "OK",
> while in the second I have to get mad at checking them all.
In case of install the defaults are set for the minimum to be able to run
apache with the default config. On upgrade i of course import the user
settings,
> Not knowing it, I'll probably hit "OK" and then get mad at checking
> them all when something breaks :)
Yell at the modules that do not provide a correct .info file ;)
> My suggested correction would be to include a description for every
> module,
probably this would be a "wontfix" but all this things in one bug make it
impossible at the moment. Let's take one step at a time.
> to initialize the selections using what is in the existing
> configuration files and to explicitly say so,
There is no need to for this, It is obvious (to me) that we do not want to
break users configs. (other than it happened for my mistake).
> so that the admin knows
> that he can safely just press "OK" if (s)he already has a working
> configuration.
They can do it now already.
Fabio
--
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues
http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp00004.html
Reply to: