tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: sh -e changes broke pkgsrc

On Mon, May 26, 2008 at 04:35:37PM +0200, Matthias Drochner wrote:
> said:
> > NetBSD's "sh" now implements both cases correctly
> > [...]
> I'm not so sure this is correct. Every other sh behaves
> as NetBSD's did before, as as bash does.

Please explain why "true && false" should be different from "false && true".

> And
> says:
> -e When this option is on, if a simple command fails for any of
>    the reasons listed in Consequences of Shell Errors or returns
>    an exit status value >0, and is not part of the compound list
>    following a while, until, or if keyword, and is not a part of
>    an AND or OR list, and is not a pipeline preceded by
>    the ! reserved word, then the shell shall immediately exit.

If an "AND list" in the above definition refers to "foo && var" why
would "true && false" terminate "bash".

        Kind regards

Matthias Scheler                        

Home | Main Index | Thread Index | Old Index