[Top][All Lists]

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

[Groff] Fwd: Re: <OK> Re: [PATCH] Use bash for several contrib scripts

From: Daode
Subject: [Groff] Fwd: Re: <OK> Re: [PATCH] Use bash for several contrib scripts
Date: Thu, 02 Jan 2014 16:06:17 +0100
User-agent: s-nail v14.5.1-28-g04da9bc

(blush) really nice bicycles..

-------- Original Message --------
Date: Thu, 2 Jan 2014 09:49:27 -0500
From: Mike Bianchi <address@hidden>
To: Steffen Nurpmeso <address@hidden>
Subject: Re: <OK> Re: [Groff] [PATCH] Use bash for several contrib scripts

On Thu, Jan 02, 2014 at 03:03:48PM +0100, Steffen Nurpmeso wrote:
>       :
> Imho it is a bug that the generated scripts
> use /bin/sh but are not compatible to a real /bin/sh.

I _strongly_ agree.
There is no man page for  sh(1) .
There is no executable for /bin/sh .  On Debian ...
          ls -l /bin/sh
        lrwxrwxrwx 1 root root 4 Mar  1  2012 /bin/sh -> dash*

And the man page for  dash(1)  says it does not conform to a documented

        The current version of dash is in the process of being changed to
        conform with the POSIX 1003.2 and 1003.2a specifications for the shell.
        Only features designated by POSIX, plus a few Berkeley extensions,
        are being incorporated into this shell.

        This man page is not intended to be a tutorial or a complete
        specification of the shell.

For those reasons, I think  #!/bin/sh  should be outlawed!
(Yeah, right.  That's going to happen.)

Still, within the groff project, could we pick one shell to be the standard?

Or am I trying to inflict order on an unorderly universe?

 Mike Bianchi
 Foveal Systems

 973 822-2085


reply via email to

[Prev in Thread] Current Thread [Next in Thread]