On 18.01.2013 15:58, Moritz Moeller wrote:
> I think this is because it calls sed which is the system's BSD sed which
> is different from GNU sed.
Thanks for the report!
The script is developed on FreeBSD, where sed(1) is not GNU sed either.
However, it has a "-r" flag for GNU sed compatibility
I think this is because it calls sed which is the system's BSD sed which
is different from GNU sed. Macports has a GNU sed (gsed) package and the
executable's name is 'gsed'.
After I installed gsed and moved /usr/bin/sed out of the way and
symlinked that to /opt/local/bin/gsed, everything worked