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

Re: Bug#142944: fixing debconf stdin bug

On Wed, 14 Jan 2004 00:38:52 -0500, Joey Hess <joeyh@debian.org> said: 

> Manoj Srivastava wrote:
>> 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 STDIN?

> This is not something that I have the least little interest in
> trying to support, for a wide variety of reasons that I will not go
> into here.

	I can understand that -- you have written debconf, and it
 probably perfectly satisfies your needs, and behaves in a fashion
 that feels absolutely natural and logical to you. but that does not
 mean that the current behaviour is one that would be optimal for
 other folks -- especially those considering writing another program
 that adheres to the debconf  spec.

To err is human, but I can REALLY foul things up.
Manoj Srivastava   <srivasta@debian.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

Reply to: