Re: Bug#176506: Make debconf mandatory for prompting the user
On Thu, Jan 16, 2003 at 02:25:40AM +0100, Josip Rodin wrote:
> On Thu, Jan 16, 2003 at 01:47:20AM +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?
It doesn't magically fix something.
Policy should document current good practice.
AFAIK most developers agree that it's a good thing to use debconf for
prompting the user and practice this in their packages (if needed).
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.
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed