On Tue, Feb 17, 2004 at 11:52:31PM -0800, Philip Brown wrote:
> On Wed, Feb 18, 2004 at 08:47:12AM +0100, Denis Barbier wrote:
> > > But you might debate that point,with the debian person who filed a bug
> > > suggesting that I needed to do it with debconf in the first place ;-)
> >
> > This had been debated several times on debian-devel, see eg.
> > http://lists.debian.org/debian-devel/2004/debian-devel-200401/msg01686.html
> > and has been clarified in debconf-devel(7):
> > note ...
> > It's best to use these only for warning about very
> > serious problems.
>
> Well.. it IS a very serious problem. It is very frustrating for a user to
> upgrade, and suddenly have the program not function, and have no idea why,
> or how to fix it.
>
> In theory, the "note" should only be displayed by debconf if the user was
> upgrading from one of the really old versions.
> So if there is no need for the note, it will never cause an action to
> take place.
> So IMO, it is one of the few really good cases to use it.
Do not forget that a user != admin, and to my mind a debconf note is
only intended to be display to the box admin.
Cheers,
--
Pierre Machard
<pmachard@debian.org> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87
Attachment:
signature.asc
Description: Digital signature