On Fri, Oct 22, 1999 at 07:11:24PM +0200, Goswin Brederlow wrote:
> Chris Lawrence <[EMAIL PROTECTED]> writes:
>
> > Therefore, I propose that we permit the use of bzip2 to compress
> > source package files (.orig.tar for non-native packages, .tar for
> > native packages). A patch to dpkg-1.4.1.1
Package: debian-policy
Version: 3.0.1.1
Severity: wishlist
I'm tired of defending the current situation where debian policy specifies
POSIX behavior for /bin/sh, but echo -n has widespread use in the Linux
community (including especially debian policy, the linux kernel source,
many debian scripts,
Raul Miller <[EMAIL PROTECTED]> wrote:
> Package: debian-policy
> Version: 3.0.1.1
> Severity: wishlist
> I'm tired of defending the current situation where debian policy specifies
> POSIX behavior for /bin/sh, but echo -n has widespread use in the Linux
> community (including especially debian po
On Mon, Oct 25, 1999 at 02:31:42PM +1000, Herbert Xu wrote:
> What about escape codes, do we require them or do we forbid them?
I think it would be a bad idea to make any recommendations on
escape codes in debian policy:
(1) We don't use them.
(2) In almost all examples we don't care if they're
On Mon, Oct 25, 1999 at 12:50:56AM -0400, Raul Miller wrote:
> On Mon, Oct 25, 1999 at 02:31:42PM +1000, Herbert Xu wrote:
> > What about escape codes, do we require them or do we forbid them?
>
> I think it would be a bad idea to make any recommendations on
> escape codes in debian policy:
>
>
On Mon, Oct 25, 1999 at 02:54:00PM +1000, Herbert Xu wrote:
> When I said escape codes, I really meant the scripts that currently
> use them with/without -e. So with your current modification to the
> policy, escape codes are no longer allowed in any #!/bin/sh script.
> Remember the kernel source
On Mon, Oct 25, 1999 at 02:54:00PM +1000, Herbert Xu wrote:
> Currently bash and ash supports -e in violation to POSIX.
Rereading my copy of chapter 4.19 of the POSIX 1003.2 draft:
4.19.3 Options
The echo utility shall not recognize the -- argument in the manner
specified by utility syntax
On Mon, Oct 25, 1999 at 01:36:26AM -0400, Raul Miller wrote:
>
> Rereading my copy of chapter 4.19 of the POSIX 1003.2 draft:
>
>
> 4.19.3 Options
>
> The echo utility shall not recognize the -- argument in the manner
> specified by utility syntax guideline 10 in 2.10.2; -- shall be
> reco
On Mon, Oct 25, 1999 at 01:36:26AM -0400, Raul Miller wrote:
> > Rereading my copy of chapter 4.19 of the POSIX 1003.2 draft:
> >
> >
> > 4.19.3 Options
> >
> > The echo utility shall not recognize the -- argument in the manner
> > specified by utility syntax guideline 10 in 2.10.2; -- shall
On Mon, Oct 25, 1999 at 02:44:57AM -0400, Raul Miller wrote:
>
> None of the text you quoted forbids supporting -e without backslashes.
IMHO it does. Firstly it's clear from the wording that all "options"
come under the operands category. So unless you've got -n as the very first
operand or you
On Mon, Oct 25, 1999 at 04:51:42PM +1000, Herbert Xu wrote:
> IMHO it does. Firstly it's clear from the wording that all "options"
> come under the operands category.
It's clear from the wording that only for the -- option is this behavior
guaranteed.
--
Raul
retitle 46516 [ACCEPTED 25/10/1999] MIME support sub-policy
forwarded debian-policy@lists.debian.org
thanks
No objections have been raised since this proposal was moved to 'AMENDMENT'
status on 04/10/1999 and it's been more than the 10 days discussion period,
so if I understand matters correctly,
Processing commands for [EMAIL PROTECTED]:
> retitle 46516 [ACCEPTED 25/10/1999] MIME support sub-policy
Bug#46516: [AMENDMENT 04/10/1999] MIME support sub-policy
Changed Bug title.
> forwarded debian-policy@lists.debian.org
Unknown command or malformed arguments to command.
> thanks
Stopping pr
On Mon, Oct 25, 1999 at 03:03:34AM -0400, Raul Miller wrote:
> On Mon, Oct 25, 1999 at 04:51:42PM +1000, Herbert Xu wrote:
> > IMHO it does. Firstly it's clear from the wording that all "options"
> > come under the operands category.
>
> It's clear from the wording that only for the -- option is t
On Mon, Oct 25, 1999 at 09:08:51PM +1000, Herbert Xu wrote:
> So, unless the first operand is -n, or if the string contains backslash
> characters, the operands are to be written to the standard output verbatim
> separated by sngle spaces with a new line at the end. If the first operand
> is -n, o
Let me state once again, this has no bearing whatsoever over the proposed
change in policy and my question about whether escape codes/-e are to be
mentioned or not. It is for purely pendantic value.
On Mon, Oct 25, 1999 at 07:24:59AM -0400, Raul Miller wrote:
> Except you elected to not quote wha
Ben Collins <[EMAIL PROTECTED]> writes:
> On Fri, Oct 22, 1999 at 07:11:24PM +0200, Goswin Brederlow wrote:
> > Chris Lawrence <[EMAIL PROTECTED]> writes:
> >
> > > Therefore, I propose that we permit the use of bzip2 to compress
> > > source package files (.orig.tar for non-native packages, .tar
On Mon, Oct 25, 1999 at 11:32:32PM +0200, Goswin Brederlow wrote:
>Ben Collins <[EMAIL PROTECTED]>writes:
>
>>On Fri, Oct 22, 1999 at 07:11:24PM +0200, Goswin Brederlow wrote:
>>>Chris Lawrence <[EMAIL PROTECTED]> writes:
>>>
Therefore, I propose that we permit the use of bzip2 to compress
>>>
18 matches
Mail list logo
