Re: starting/stopping daemons in package scripts

1999-09-25 Thread Joey Hess
Remco Blaakmeer wrote: > > For example, by using reload in the postinst, the downtime of services can > > probably be minimized at an upgrade (instead using stop in the prerm and > > start in the postinst). > > s/reload in the postinst/restart in the postinst/ > > 1. 'reload' is not a mandatory o

weekly policy summary

1999-09-25 Thread Joey Hess
Here's what's been happening on debian-policy this week. Please let me know if you think any proposals have a consensus. Note: for details of the policy process, see http://www.debian.org/~srivasta/policy/ch3.html. Also, this summary is available on the web at http://kitenet.net/~joey/policy-week

Bug#45561: PROPOSAL] tech-ctte: /usr/share/doc

1999-09-25 Thread Joey Hess
Julian Gilbey wrote: > > The technical committee has been asked to resolve the issue of what to do > > with /usr/share/doc. I propose we actually adopt their decision. I > > propose further that we don't bother to have discussion--we're past all > > that. The decision has been made and while pos

Re: Packages should not Conflict on the basis of duplicate functionality

1999-09-25 Thread The Doctor What
On Fri, Sep 24, 1999 at 11:13:27AM -0400, Scott K. Ellis wrote: > Okay, then solve the problem of which one should actually work on the > standard port? You can't use update-alternatives if the software is > launched in a different manner. If you have such an advanced setup, it > isn't really tha

Re: Packages should not Conflict on the basis of duplicate functionality

1999-09-25 Thread Raul Miller
On Fri, Sep 24, 1999 at 11:34:28PM -0500, The Doctor What wrote: > I do not like the idea of a daemon starting up with a default > configuration that I have not double checked upon installation. I > consider automatically starting with no choice a misfeature. I think I agree. I got a rude start

Re: Packages should not Conflict on the basis of duplicate functionality

1999-09-25 Thread Joey Hess
The Doctor What wrote: > Why shouldn't *all* daemon packages ask these questions, and whether to even > run *upon install*? Because we need to decrease the number of questions asked at install time, not increase it. -- see shy jo

Re: Packages should not Conflict on the basis of duplicate functionality

1999-09-25 Thread Seth R Arnold
On Sat, Sep 25, 1999 at 01:02:44AM -0700, Joey Hess wrote: > The Doctor What wrote: > > Why shouldn't *all* daemon packages ask these questions, and whether to even > > run *upon install*? > > Because we need to decrease the number of questions asked at install time, > not increase it. How about

Bug#45561: PROPOSAL] tech-ctte: /usr/share/doc

1999-09-25 Thread Roland Rosenfeld
On Mon, 20 Sep 1999, Joseph Carter wrote: > The technical committee has been asked to resolve the issue of what > to do with /usr/share/doc. I propose we actually adopt their > decision. I second this. > I propose further that we don't bother to have discussion--we're > past all that. And I se

Re: Packages should not Conflict on the basis of duplicate functionality

1999-09-25 Thread Joey Hess
Seth R Arnold wrote: > How about add one question: "Automatically start all daemons: [Y/n]" > > If they answer yes, then no questions. If they answer no, ask as many > questions as you want. :) > > Of course, the downside of this particular question is ... not *all* daemons > should be automatica

Bug#45561: PROPOSAL] tech-ctte: /usr/share/doc

1999-09-25 Thread Antti-Juhani Kaijanaho
On Fri, Sep 24, 1999 at 07:38:23PM -0700, Joey Hess wrote: > I think someone needs to write a policy diff. It can use how debhelper does > things as the reccomended method, without metioning debhelper. For example: I second this proposal assuming it is amended with this or equivalent diff. -- %%

Re: starting/stopping daemons in package scripts

1999-09-25 Thread Philip Hands
Joey Hess <[EMAIL PROTECTED]> writes: > This just shows why policy should not specify. This is an area where the > maintainer should be allowed to use common sense. > > If you maintain a package, you _wrote_ the init script. You know if it > supports reload, and if so, you use it. Otherwise, you

Re: [forward] FHS pre-2.1 draft #3 on web site

1999-09-25 Thread Philip Hands
Raul Miller <[EMAIL PROTECTED]> writes: > Our job is to give them a better alternative. > > > The fact that the FHS makes their existence optional, means that it's > > not insisting that we install them. > > True, but this doesn't solve any problems as far as I can see. The status quo is that t

Bug#45561: PROPOSAL] tech-ctte: /usr/share/doc

1999-09-25 Thread Joseph Carter
On Fri, Sep 24, 1999 at 08:24:55AM +0300, Antti-Juhani Kaijanaho wrote: > > As for the technical implementation of the tech-ctte decision, I propose > > we use joeyh's implementation found in any recently uploaded debhelper > > package. > > Please clarify this. Preferably give the diff you want t

Bug#45561: PROPOSAL] tech-ctte: /usr/share/doc

1999-09-25 Thread Joey Hess
Joseph Carter wrote: > On Fri, Sep 24, 1999 at 08:24:55AM +0300, Antti-Juhani Kaijanaho wrote: > > > As for the technical implementation of the tech-ctte decision, I propose > > > we use joeyh's implementation found in any recently uploaded debhelper > > > package. > > > > Please clarify this. Pr

Re: weekly policy summary - Data section (#38902)

1999-09-25 Thread Bob Hilliard
> Data section (#38902) > * Consensus. > * Proposed on 3 Jun 1999 by Darren O. Benham; seconded by Peter S > Galbraith and Peter Makholm. > * "Since there is interest in packaging census data, maps, genome > data and other huge datasets I and since most people agreed that > dropp