Re: Solaris and sed: Too many commands, last: s/\n//

From: Jeffrey Walton <noloader@gmail.com>
Date: Mar 12, 2019, 01:07 UTC
Message-ID: <CAH8yC8kHhhWA+ONv17LdLpvy6ubH3CTvJ6=ehP5MQLi_=n1=bQ@mail.gmail.com>
In-Reply-To: <20190311222805.GA6215@flurp.local>

On Mon, Mar 11, 2019 at 6:28 PM Eric Sunshine <sunshine@sunshineco.com> wrote:

Show 23 quoted lines

>
> On Mon, Mar 11, 2019 at 05:43:55PM -0400, Jeffrey Walton wrote:
> > On Mon, Mar 11, 2019 at 5:15 PM Eric Sunshine <sunshine@sunshineco.com> wrote:
> > > On Mon, Mar 11, 2019 at 4:32 PM Jeffrey Walton <noloader@gmail.com> wrote:
> > > > I enabled self tests for Solaris. Solaris has some anemic utilities so
> > > > I put /usr/gnu/bin first on-path.
> > >
> > > The first question is if you are really running GNU 'sed'? My guess is
> > > "no, it's still picking up Solaris's 'sed'".
> >
> > I believe so. After modifying PATH, command -v returns:
> >
> >     Solaris tools:
> >          sed: /usr/gnu/bin/sed
> >          awk: /usr/gnu/bin/awk
> >         grep: /usr/gnu/bin/grep
> >
> > (This was added to my scripts to confirm).
> ...
>
> > Maybe Git would benefit from SED, AWK and GREP variables like PERL.
>
> Very possibly.

Another potential workaround is to use Perl. Perl is already a prerequisite, it get passed to the test gear through PERL_PATH, and it avoids Solaris' anemic tools.

Sadly my Perl sucks. You would be disappointed if I tried to whip up a patch.

Jeff