Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

location of bash shell on OpenBSD fails #497

Closed
rbucker opened this issue May 4, 2012 · 3 comments
Closed

location of bash shell on OpenBSD fails #497

rbucker opened this issue May 4, 2012 · 3 comments

Comments

@rbucker
Copy link

rbucker commented May 4, 2012

When BASH is installed on an OPENBSD system the default location is /usr/local/bin/bash and unless the programmer creates a symlink running the tests is going to fail since it expects bash to be located in /bin.

@pietern
Copy link
Contributor

pietern commented May 7, 2012

Does OpenBSD have /usr/bin/env? If so, it would be better to use that to resolve the path to bash instead of defaulting to a commonly used location.

@jbergstroem
Copy link
Contributor

$ uname -a
OpenBSD obsd-test.foo 5.1 GENERIC#160 i386
$ which env
/usr/bin/env

@hypersoft
Copy link

Don't be stupid. Just create a symlink it will save you lots of editing and serve to keep bash scripting portable. If you write a script I can use in linux I don't want to have to rewrite it, If I write a script you can use in OpenBSD I don't want you to have to rewrite it. Thoughtfulness and usefulness go hand in hand.

Bash is a GNU/Linux tool, and if you want to use it you should see its standards as acceptable and they are harmless (actually useful)

I have written a makefile you can distribute with your scripts that also outlines the very good reasons you should not be forcing people to rewrite scripts or use /usr/bin/env

I write tons of bash scripts and I'm not going to cater to making the world less portable. I encourage all users of bash to to approach that concept sensibly and responsibly.

http://pastebin.com/bp7Cf6Rv

@badboy badboy closed this as completed Jul 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants