Re: Bug#142944: fixing debconf stdin bug
On Tue, 13 Jan 2004 18:14:38 -0500, Joey Hess <email@example.com> said:
> Manoj Srivastava wrote:
>> Policy merely states that you must needs use a debconf like
>> mechanism to talk to the user -- something that follows the policy
>> spec. That does not imply that debconf has sole rights -- one could
>> well have an alternate mechanism to talk to the user, which is
>> policy compliant, and not debconf.
>> Hence, stealing away stdin is a bug.
> No, policy specifies that scripts should prompt by communicating
> with a program such as debconf which implements the Debian
> Configuration management specification. That specification, as I
> pointed out before, requires that said communication be done using
> Debconf does not "steal" anything. If you choose to use it, you
> communicate with it using stdio.
What if I chose to use two such frontends? There is nothing in
policy that states that each script should communicate with one and
only one debconf like program.
In theoryu, I can ask a dozen questions, each using a
different debconf like program -- and be policy compliant.
How does the second, third and so forth program get hold of
"If people are good only because they fear punishment, and hope for
reward, then we are a sorry lot indeed." Albert Einstein
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C