On 16/09/2007, Roger Marquis <[EMAIL PROTECTED]> wrote: > On Sun, 16 Sep 2007, Shawn Walker wrote: > > The people that created this problem are the idiots that put > > #!/bin/sh at the top of their script and assume that means bash, > > when it obviously isn't. > > Exactly what I'm talking about Shawn. And I would have agreed with > you up to five or six years ago. But the world has changed. The > choice today is whether to go with that change or try to lead it > in a different direction. IME the latter approach requires a large > market share. Otherwise, decrease compatibility before attaining > minimum mindshare, is certain to fail.
I think I'm just going to have to agree to disagree. I just don't see this as being as big of an issue as you seem to imply. > > That's one of the reasons everyone at the company I work at is > > required to specifically indicate which shell they're using via > > #!/bin/ksh #!/bin/sh #!/bin/bash, etc. Since the scripts may be > > run on other systems... > > And what about those systems that do not install bash, ksh, ... in > /bin? Or are the other systems you're referring to managed by the > same company writing the scripts? Bottom line, today as in the > past, if you're writing for cross-platform compatibility there is > no option other than "#!/bin/sh". Sorry, I didn't mean, literally, /bin, /usr/bin actually in this case. But yes, they are all managed by the same company. The reason we are required to do so is because of SCO boxes, RedHat 7, etc. We do not have a unified environment (yet). -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
