[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#206684: mandatory use of debconf for user prompting a release goal for squeeze



Hi,

On Donnerstag, 19. März 2009, Russ Allbery wrote:
> >         Package maintainer scripts may prompt the user if necessary.
> >         Prompting must be done by communicating through a program, such
> >         as debconf, which conforms to the Debian Configuration
> >         Management Specification, version 2 or higher, unless no such
> >         interface is available when they are executed.

         Package maintainer scripts may prompt the user if necessary.
         Prompting must be done by communicating through a program, such
         as debconf, which conforms to the Debian Configuration
         Management Specification, version 2 or higher. Exempted from using   
         such a programm are required/essential packages if no such
         interface is available when they are executed.

> Should we require that non-essential packages depend on debconf if they're
> going to do prompting?  That wording implies to me that any package could
> check whether it was already installed (without a dependency) and fall
> back on non-debconf prompting, but I think that should only be permissible
> for essential packages.

See the proposal above.

> The only other thing that I'm not sure about is what to do about preinst
> scripts.  Are we requiring debconf for preinst prompting (and hence
> requiring a Pre-Depends) for non-essential packages?

As we require it for any prompting, this includes preinst, and as stuff used 
in preinst needs to be a Pre-Depends, I think this is clear.


regards,
	Holger

P.S. Andrew, thanks! 

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: