[Rcpp-devel] Rcpp Armadillo's configure script's hashbang

Dirk Eddelbuettel edd at debian.org
Sat Feb 28 20:55:43 CET 2015


On 28 February 2015 at 19:34, Ze Loff wrote:
| 
| Hi
| 
| Can #!/bin/bash be replaced by something more portable (e.g. #!/bin/sh)
| on the configure script? Since I don't think that there are any
| bash-isms on the configure script, and that most UNIX-like OS have
| either some version of the Bourne Shell or link /bin/sh to a compatible
| shell (e.g. OS X hardlinks /bin/sh to /bin/bash), I believe switching to
| #!/bin/sh would improve portability.
| 
| (In my case, installation of RcppArmadillo failed on OpenBSD since I
| don't have bash installed, but it installed fine from source after
| changing to #!/bin/sh)

That is rather unlikely as I explained here 

   https://github.com/RcppCore/RcppArmadillo/pull/35

when rejecting that PR. Which came unannounced and undiscussed, which is
generally a bad idea; always preferable to file an issue ticket fist, or
discuss here as you did.

Changing this creates extra work for me as I need to clean the shell script
of things bash has for free.  I happen to like bash as a basic shell.

If your system is large enough to have room for R and extra packages, I'd
argue that it should have room for bash too: per the respective Debian/Ubuntu
packages size, bash is actually smaller than RcppArmadillo.  And if you
really can't then you can always locally patch the tarball.

At some point this test will go away and we'll just assume a good enough LAPACK.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org


More information about the Rcpp-devel mailing list