From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: ITP checkbashisms -- Check for bashisms in /bin/sh scripts
Date: Sun, 05 Feb 2012 21:37:00 -0000 [thread overview]
Message-ID: <1328477811.7876.6.camel@YAAKOV04> (raw)
In-Reply-To: <4F2EDB87.5090605@cwilson.fastmail.fm>
On Sun, 2012-02-05 at 14:41 -0500, Charles Wilson wrote:
> We're not debian, and don't explicitly exclude the use of bashism in
> *ALL* [/usr]/bin/*.sh scripts. Even debian doesn't disallow bashisms i
> *usr*/bin/ scripts -- and as /bin == /usr/bin on cygwin, we can't realy
> distinguish between /bin/*.sh and /usr/bin/*sh. Some of our scripts, in
> fact, have sh-bang lines explicitly requiring bash (e.g. cygport).
>
> So...I'm not sure this is a totally useful tool for cygwin; it might
> lead to unnecessary list traffic:
>
> "Hey, checkbashisms complains about /usr/bin/cygport, please fix..."
>
> I realize this doesn't require votes as it is already in debian, and I
> certainly have no veto power, but if it did require votes I'd be giving
> it a '0' not a '+1'.
You make valid points, but I suppose it would still be useful for
someone writing sh scripts on Cygwin to check their portability to
stricter /bin/sh shells on other systems.
So while I'm hardly overwhelmed by the necessity for adding this
package, its not completely useless on Cygwin either.
Yaakov
next prev parent reply other threads:[~2012-02-05 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 8:55 Jari Aalto
2012-02-05 19:42 ` Charles Wilson
2012-02-05 21:37 ` Yaakov (Cygwin/X) [this message]
2012-02-06 11:21 ` Corinna Vinschen
2012-02-11 11:05 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1328477811.7876.6.camel@YAAKOV04 \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).