Re: set -e vs. #!/bin/sh -e

To: srivasta@datasync.com (Manoj Srivastava)
Cc: debian-policy@lists.debian.org
Subject: Re: set -e vs. #!/bin/sh -e
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Sun, 17 May 1998 11:48:06 +1000 (EST)
Message-id: <[🔎] 199805170148.LAA05292@gondor.apana.org.au>
In-reply-to: <[🔎] 87u36qrsrq.fsf@tiamat.datasync.com> from Manoj Srivastava at "May 16, 98 01:10:33 pm"

Manoj Srivastava wrote:

<good reasons deleted>
 
> 	I see no benefit in making it easy to turn error detection
>  off. It should be done as a matter of last resort. In that case, they
>  can edit (a copy of) the script.
> 
> 	So, I guess I object to anything like this ever getting into
>  the Policy standard.

OK, I can live with that.

-- 
Debian GNU/Linux 1.3 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to:

References:
- Re: set -e vs. #!/bin/sh -e
  - From: Manoj Srivastava <srivasta@datasync.com>

Prev by Date: Re: Purging database packages
Next by Date: Uploading updated documentation package to frozen
Previous by thread: Re: set -e vs. #!/bin/sh -e
Next by thread: Uploading updated documentation package to frozen
Index(es):
- Date
- Thread