Re: Bug#176506: Make debconf mandatory for prompting the user
On Thu, Jan 16, 2003 at 02:40:39AM +0100, Adrian Bunk wrote:
> > > The problem is that within the rules of your policy every single of your
> > > over thousand maintainers can decide how he wants to maintain his
> > > packages. Currently a maintainer can simply refuse to use debconf and
> > > _noone_ can force him to use debconf. There are bugs with patches like
> > > e.g. #127961 that are already ignored for a year or longer.
> > And putting a "must" in the Policy magically fixes all such issues?
> Policy should document current good practice.
That statement does not equal the above statements. Current good practice
can and should be documented with proper means. It should not be suddenly
imposed on everyone, making a number of packages subject to filing serious
bugs, when in reality they are not.
> But as long as something isn't required by your policy every single of
> your over thousand developers is able to say "I don't want this in my
> packages" even when working patches are available.
Once again, your reasoning is incorrect. Developers can very well ignore
policy if they're either unnoticed or the technical committee has not
decided otherwise. Policy going from saying nothing to saying "must" or
"required" is the wrong way to settle such an issue.
2. That which causes joy or happiness.