Re: Bug#176506: Make debconf mandatory for prompting the user

[Junichi Uekawa <dancer@netfort.gr.jp>]

> > 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?

I think that is documenting current practice, yes.

At least for base packages we have an unwritten policy that 
all packages must configure with debconf or 
required to be noninteractive when DEBIAN_FRONTEND=noninteractive
or not fail when it is fed with input from < /dev/null,
for the task of debootstrap.


regards,
	junichi