[Pkg-puppet-devel] Bug#509566: Bug#509566:

[Faidon Liambotis]

Thom May wrote:
> On Tue, Jan 13, 2009 at 4:26 PM, Faidon Liambotis <paravoid at debian.org> wrote:
>> Thijs Kinkhorst wrote:
>> Sometimes people just install a package to read documentation/the
>> manpages/read the code etc.
>>
>> It should either need manual work for the init script to start (i.e.
>> disable autostart) or have a sensible default for the loop delay.
>>
> I don't think that we should be assuming that case, or defaulting to it.
> It's a reasonable assumption that most people installing something like puppet
> are intending to use it, and that should be the case that works out of the box.
> I don't think a debconf question is unreasonable, but I definitely
> don't think that's
> something we should be thinking about (or need) in the lenny timescale.
Basically, with your latest upload, you have changed the behavior over
two defaults:

a) The upstream default of "waitforcert", from 120s to 5s

b) The Debian default in the versions so far which tried /once/ and then
   exited without looping *at all*. That was what puppet <= 0.24 did
   with "-w 0" and that's what the documentation still (incorrectly)
   says.

You are /changing/ the status quo, especially wrt the etch package.
I'm fine with you doing it as the maintainer and even if I don't agree
with your choice I don't intend to go very far with my disagreement.

But please, don't act as if this was the behavior of the package all
along or as if I'm saying something totally unreasonable.

Anyway, I think we can live for now until a proper debconf prompt is
made, even if it's not a real question but just used for preseeding.
"wishlist" is a bit of an understatement though, IMHO.

Regards,
Faidon

1: When Debian defaulted to "-w 0" and that meant something totally
   different that is.