Ola Lundqvist <[EMAIL PROTECTED]> (21/04/2006): > On Fri, Apr 21, 2006 at 12:31:03AM +0200, Thomas Huriaux wrote: > > Ola Lundqvist <[EMAIL PROTECTED]> (20/04/2006): > > > On Thu, Apr 20, 2006 at 07:32:00PM +0200, Thomas Huriaux wrote: > > > > All of your debconf notes are typical Debconf abuse. Such notes have no > > > > added value during the package configuration process. The > > > > information they contain should go to the package documentation > > > > and should never stop the installation process. > > > > > > You have misunderstood the purpose of this package suite. > > > > > > The harden packages provide _nothing_ more than a guide for > > > the system administrator with conflicts, dependencies and > > > debconf output. > > > > > > That is why I'll now mark this package as wontfix. > > > > > > But if you can give me a good explanation on why I should remove > > > a specific debconf question then I may change my mind. I have > > > checked the debconf output and can not see that it is anything > > > wrong with them. > > > > You are speaking about debconf questions, but you are only using debconf > > notes which are not related with the installation/configuration of the > > package. > > Debconf is made to configure a package, not to provide documentation. > > Notes or questions. The package do not provide more than help to the > administrator. > > > > The only thing I can see is that maybe the priority can be > > > discussed, but I think it is valid to have medium for the more > > > important ones and low for the less important. > > > > > > If you want to install a system without being stopped by this > > > kind of questions you can change the debconf input level or > > > change the frontend for debconf. > > > > I don't want to install a system without being stopped by questions, I > > want to have to care only about the configuration of the packages I'm > > installing during the installation process. So, if the installation stop, > > it should only to prompt for something needed to configure the package > > or to mention something *very* important I have to do after the > > installation of the package to get it working. > > Yes but it is important for hardening of the system to follow the instructions > mentioned. Without it is not much use of the package.
But if your package does nothing else than providing help to the administrator, why don't you create a simple binary to display these instructions? I still don't understand the reason to display these instructions during the installation process, at it does not change anything for the package usability. -- Thomas Huriaux
signature.asc
Description: Digital signature
