News for hackers. Stuff that matters.
Re:Use long flags when scripting by jerf on Monday February 04, 2013 @10:57AM (#5164732)
It's always a cost/benefits analysis. I think for a lot of us, the cost/benefit goes something like this:

"Will I ever have to read and modify this script again? Effectively-100% likely. Will this script ever run anywhere that I don't have the GNU toolchain? Effectively-0% likely."

It's a no-brainer at that point.

If you can't say that second part honestly, reconsider, but a lot of us can.

Re:Use long flags when scripting by lamby on Monday February 04, 2013 @11:13AM (#5164857)
> Will this script ever run anywhere that I don't have the GNU toolchain? Effectively-0% likely.

Not really. A lot of stuff broke when /bin/sh moved to a POSIX-compatibile shell rather than Bash.

Re:Use long flags when scripting by njharman on Monday February 04, 2013 @11:52AM (#5165171)
No a lot of stuff broke because people depended on implicit rather than being explicit.

    #!/bin/bash
Re:Use long flags when scripting by Wilya on Monday February 04, 2013 @12:16PM (#5165405)

  wilya@home $ /bin/bash
  zsh: no such file or directory: /bin/bash
  wilya@home $ which bash
  /usr/local/bin/bash
(Yes, I'm annoyed when I see #!/bin/bash, especially on scripts which are otherwise basic enough to be portable everywhere)
Re:Use long flags when scripting by dfox on Monday February 04, 2013 @12:31PM (#5165564)
It is still better to write #!/bin/bash for bashism using scripts than #!/bin/sh. I recently had to run sed -i (well, another GNUism) 1s%/sh%/bash% on bunch of customer's scripts to make them work on debian. At least when script wants /bin/bash it is going to fail cleanly (and not in the middle after modifying random things) and with mostly meaningful error.
Re:Use long flags when scripting by wollw on Tuesday February 05, 2013 @01:07AM (#5169426)
It's probably safer to use:

    #!/usr/bin/env bash
Assuming env is installed (I believe I had to install a package on OpenBSD to use it) this will find the first instance of bash in the PATH.
Re:Use long flags when scripting by atsaloli on Tuesday February 05, 2013 @01:25AM (#5169476)
How do you know env is in /usr/bin rather than in /bin or /usr/local/bin? I'm just curious...
Re:Use long flags when scripting by wollw on Tuesday February 05, 2013 @01:32AM (#5169495)
You don't, but I've run into more problems with bash being in unexpected places than env.
Re:Use long flags when scripting by atsaloli on Tuesday February 05, 2013 @05:03AM (#5169956)
Right on, thanks.
Re:Use long flags when scripting by ralph on Tuesday February 05, 2013 @08:25AM (#5170494)
Good question. I've used systems, e.g. AIX, where env(1) was in /bin.
Re:Use long flags when scripting by X-Istence on Monday February 04, 2013 @11:14AM (#5164860)
And now porting your script to non GNU such as BSD becomes a pain in the behind ... whereas before maybe only one or two commands would have had to change, now it will be most if not all.
Re:Use long flags when scripting by jerf on Monday February 04, 2013 @12:11PM (#5165350)
When I mentioned "GNU", I think it sort of implied that I am aware of the existence of non-GNU toolchains.

I really am not worried about that in my world. The dependencies on Linux go a great deal deeper than the GNU toolchain. YMMV.

Re:Use long flags when scripting by papsosouid on Monday February 04, 2013 @02:39PM (#5166531)
>Will this script ever run anywhere that I don't have the GNU toolchain? Effectively-0% likely.

That's not the case for most people though. I can't even remember the last time I saw even a tiny project assume the world is all "whatever gnu/linux distro I happen to use". Tons of people use linux distros that aren't ubuntu, tons of people use OSX, tons of people use a BSD.