Some of the comments are really curious. First of all the /bin to /usr/bin symlink on usrmerged systems will be NEVER removed as there is a FHS standard.
Second, the use of "#!/usr/bin/bash" or similar is absolutely bad style - you could use that for your private scripts, but if you publish them everybody with a not usrmerged distribution has to "fix" it.
Some really still think that /bin/sh points to /bin/bash by default. Little hint: since several years most distributions use dash for sh because of speed reasons - and for my part I had no big issues to remove most bashisms. The "&>" example is one of those trivial changes - it is shorter but if this is the "only" reason why you need bash in first case then you do something wrong. My goal is to write mainly POSIX compatible scripts which can be run by dash, some scripts use bash tricks, those have got bash in the shebang. Using bash all the time is bad style IMHO.
Last thing to mention is that all projects which want that there code is packaged by different distributions have to write portable code. That's becoming a little bit harder if you do some checks in a way that will only work on usrmerged systems. As many of you should know, I don't use Fedora or Arch to write my own scripts and most my scripts are not used outside of Kanotix (or Debian based systems) but I still write em as portable as reasonable - what should be the reason to write code that only runs on the latest distro of choice if the changes needed to write portable code are trivial?!
Second, the use of "#!/usr/bin/bash" or similar is absolutely bad style - you could use that for your private scripts, but if you publish them everybody with a not usrmerged distribution has to "fix" it.
Some really still think that /bin/sh points to /bin/bash by default. Little hint: since several years most distributions use dash for sh because of speed reasons - and for my part I had no big issues to remove most bashisms. The "&>" example is one of those trivial changes - it is shorter but if this is the "only" reason why you need bash in first case then you do something wrong. My goal is to write mainly POSIX compatible scripts which can be run by dash, some scripts use bash tricks, those have got bash in the shebang. Using bash all the time is bad style IMHO.
Last thing to mention is that all projects which want that there code is packaged by different distributions have to write portable code. That's becoming a little bit harder if you do some checks in a way that will only work on usrmerged systems. As many of you should know, I don't use Fedora or Arch to write my own scripts and most my scripts are not used outside of Kanotix (or Debian based systems) but I still write em as portable as reasonable - what should be the reason to write code that only runs on the latest distro of choice if the changes needed to write portable code are trivial?!
Comment