Re: Bug#169979: kdrill package in a very bad shape
On Wed, Feb 18, 2004 at 12:49:43AM -0800, Philip Brown wrote:
> On Wed, Feb 18, 2004 at 09:24:03AM +0100, Pierre Machard wrote:
> > On Tue, Feb 17, 2004 at 11:52:31PM -0800, Philip Brown wrote:
> > > 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.
>
> True. Except when it is effectively a single-user box.
> But either way, it is important to make this sort of stuff blindingly
> obvious, because as I mentioned, tracking it down gets tricky.
> Heck, after the next official debian release (2005? heh, heh) I'll take it
> out, in unstable. But for now, its about the best way I can think of.
In a multi-user environment, or if for any reason user has a debconf
priority > high, or if he gets bored by reading lots of useless debconf
questions when upgrading from woody and did not pay attention to this
one, or if he does not remember this note when he launches his package
two weeks later, in all these cases, user won't have a second chance,
this information is no more available.
This is certainly not a good solution, this information *must* be
written somewhere (changelog, README.Debian, NEWS.Debian, or elsewhere).
And when this is done, it may become obvious that this debconf note
can be dropped.
Denis
Reply to: