Using #!/usr/bin/env bash solves this, and is consistent with how the
perl and python shebangs look like in the tree.
What is the exact case you are fixing with these patches? I am fine with
merging them generally, I just want to understand why and where you need
it.
In that particular case, it improves interactively building on NixOS
(which doesn't have /bin/bash).
We can patch shebangs during a package build, but having shebangs
working out of the box after cloning a git checkout really helps while
tinkering.
Also, it just feels right, given we do the same with `/usr/bin/env perl`
and `/usr/bin/env python` there aswell.
Florian
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
