Re: Private-only debconf templates for preseeding

2009-01-11 Thread Christian Perrier
Quoting Frans Pop (elen...@planet.nl): > IMO the use you describe can be valid in particular cases. > > One example would be when the setting is intended to only influence > behavior of the maintainer scripts during installation of the package as > part of system installation using Debian Insta

Re: Private-only debconf templates for preseeding

2009-01-11 Thread Frans Pop
Russ Allbery wrote: > My initial reaction was that anything that's worth making available for > configuration via preseeding is worth a low-priority debconf prompt, and > that having preseeding be the only interface is a weird way to use > debconf. IMO the use you describe can be valid in particul

Re: Private-only debconf templates for preseeding

2009-01-11 Thread Steve Langasek
On Sun, Jan 11, 2009 at 07:25:03PM -0800, Russ Allbery wrote: > Hello everyone, > The background for this question is Lintian Bug#492626. > There are several packages in the archive that use private debconf > templates where the only interface to them is preseeding. Examples > include the readah

Private-only debconf templates for preseeding

2009-01-11 Thread Russ Allbery
Hello everyone, The background for this question is Lintian Bug#492626. There are several packages in the archive that use private debconf templates where the only interface to them is preseeding. Examples include the readahead package (where the preseed was added for Debian Edu) and cpufrequtil