Fix portability issue

[seliopou]

• Use link instead of cp -l on OS X, since the -l flag is not supported.
• Change shebang to lookup bash in PATH. Ran across this problem on FreeBSD 9.0.

[lmartinking]

Can you split out the second commit (cd926b7), and I'll merge that one.

[seliopou]

Happy to do that, but I have two questions:

1. Why is cp -l used instead of ln in local_file_add?
2. What in particular about the first commit do you object to?

My goal in both commits is to make this project more portable. Since day-to-day I use OS X, I have an interest in seeing that portability issue resolved. Can you provide some feedback on the first commit so both myself and others using OS X can use this project out of the box?

[lmartinking]

If you use cp -l it will hard link the file if possible. I'm not sure what functionality the OS X ln command provides.

link seems to belong to coreutils, I am not sure if that is present by default in OS X.

[seliopou]

ln will make a hard link and is available in OS X. Should I change local_file_add to use ln instead of cp -l for all platforms?

[seliopou]

Ping.

Any plans on merging this, or any suggestions on how to change the merge request?

[seliopou]

One last ping.

The way that use use ln in this project will create a hard link, just like cp -l will on OS X.

At the time of this writing you have two open pull requests for OS X support (as well as FreeBSD). Do you intend on accepting patches to that will fix portability issues, or should those of us that need to work across multiple platforms organize a fork that will accept these sorts of changes?