Bug#42052: Bug#45052: [OLD PROPOSAL] /var/mail and /var/spool/mail

2001-02-26 Thread Nicolás Lichtmaier
> Comments, seconds anyone? I second this.

Bug#42052: Bug#45052: [OLD PROPOSAL] /var/mail and /var/spool/mail

2001-02-26 Thread Santiago Vila
On Mon, 26 Feb 2001, Julian Gilbey wrote: > Section 12.6: the para which currently reads: > >The mail spool is `/var/spool/mail' and the interface to send a mail >message is `/usr/sbin/sendmail' (as per the FHS). ... > > should be changed to: > >The mail spool is `/var/mail' and the i

Re: should vs must

2001-02-26 Thread Anthony Towns
On Mon, Feb 26, 2001 at 11:25:41PM +, Julian Gilbey wrote: > MUST -> RC if it doesn't conform > SHOULD -> Normal/RC bug if it doesn't conform, unless there's a > really good reason not to conform > will-be-MUST -> eventually it will be an RC bug not to conform, but >

Re: should vs must

2001-02-26 Thread Anthony Towns
On Mon, Feb 26, 2001 at 06:15:02PM -0500, Sam Hartman wrote: > There is an important difference between how you are viewing should > and how the current policy document views should. I tend to notice > this difference because of work within the IETF, but I believe my > interpretation is suppor

Re: should vs must

2001-02-26 Thread Julian Gilbey
On Mon, Feb 26, 2001 at 06:15:02PM -0500, Sam Hartman wrote: > One of the more obvious reasons for not following a should guideline > is that it's a new guideline and the maintainer hasn't gotten around > to following it. However, I suspect there are significant classes of > guidelines that will a

should vs must

2001-02-26 Thread Sam Hartman
> "Anthony" == Anthony Towns writes: Anthony> --zYM0uCDKw75PZbzx Content-Type: text/plain; Anthony> 2) Sometimes it's appropriate to raise the bar on what Anthony> we want included in Debian; that's what the difference Anthony> between "MUST" and "SHOULD" is meant to reflect

Bug#42052: Bug#45052: [OLD PROPOSAL] /var/mail and /var/spool/mail

2001-02-26 Thread Julian Gilbey
I was looking through old proposals, and saw this one. It discusses changing policy to refer to /var/mail instead of /var/spool/mail. The discussion sort of hung, but in the meantime, events have overtaken it: both base-files and libc6 essentially do the following: if /var/spool/mail is a direct

Bug#87711: PROPOSAL] Clarification of example configuration files

2001-02-26 Thread Julian Gilbey
On Mon, Feb 26, 2001 at 03:05:19PM +0100, Santiago Vila wrote: > > The reason I'm suggesting this is that there is talk of dpkg being > > able to selectively ignore (not install) certain directory trees. > > Now, if someone decides to ignore /usr/share/doc, the original method > > will break, but t

Bug#87711: Message Undeliverable!

2001-02-26 Thread badmail
The email you sent was routed to our server, but there were no recipients at this domain. Please check the address and send the message again. Thanks. Here are the recipients: [EMAIL PROTECTED]

Bug#87711: PROPOSAL] Clarification of example configuration files

2001-02-26 Thread Santiago Vila
On Mon, 26 Feb 2001, Julian Gilbey wrote: > Package: debian-policy > Version: 3.5.2.0 > Severity: wishlist > > [Following from a thread on -mentors] > > The question: can you have a default configuration file in > /usr/share/doc which is copied by the postinst to /etc if it does not > yet exist? >

Bug#87711: [PROPOSAL] Clarification of example configuration files

2001-02-26 Thread Julian Gilbey
Package: debian-policy Version: 3.5.2.0 Severity: wishlist [Following from a thread on -mentors] The question: can you have a default configuration file in /usr/share/doc which is copied by the postinst to /etc if it does not yet exist? On Mon, Feb 26, 2001 at 01:21:06PM +0100, Ove Kaaven wrote: