Re: [sed] command failure? Porting a project to FreeBSD

On 07/06/2017 09:40, blubee blubeeme wrote:
> Ahhh, that was it. Doing a find and ask to replace all instances of sed
> with gsed passed that part.
> 
> By the way, is knowledge like this written down somewhere centralized or is
> it just floating in the ether?

>From my experience of porting Ceph....
(And I agree with HPS, that if it looks a like, it does not have to be
the same.)

Most of these thing you have to find out on your own. But that is also
the fun of porting: issue arise from the strangest of corners.
Regular expression are among the most notorious, some of the Linux tools
also use Perl REs. Something the basic FreeeBSD will not do, since it
requires pulling Perl into base.

So for most of the tools, there is also a GNU equivalent, so that is
usually the first thing to look at.

Even more tricky are the tools you can install, but hat the same name as
their base counterpart. Like getopt, where the packaged one understands
a completely different set of options.
Not sure if you will be running into bash, but that ends up in
/usr/local/bin, whilest just about every script expects /bin/sh to be bash.

Even things like /usr/bin/env do not work the same way, and or have the
same parameters. So even there it does not always help.

--WjW