Re: NetBSD's sed is not gsed (Was: Re: pkg/45752: security/gnome-keyring does (still) not build)

[Steven Drake <sbd%NetBSD.org@localhost>]

On Thu, 29 Dec 2011, Joerg Sonnenberger wrote:

> On Fri, Dec 30, 2011 at 10:31:32AM +1300, Steven Drake wrote:
> > 
> > On Wed, 28 Dec 2011, noud4%home.nl@localhost wrote:
> > 
> > > host055# ls -l .tools/bin/gsed .tools/bin/sed
> > > lrwxr-xr-x  1 root  wheel  12 Dec 28 17:25 .tools/bin/gsed -> /usr/bin/sed
> > > lrwxr-xr-x  1 root  wheel   4 Dec 28 17:26 .tools/bin/sed -> gsed
> > 
> > Why is gsed pointing to /usr/bin/sed it's not GNU sed it's NetBSD sed?
> 
> Because it's a bit of a misname. For almost every case, a modern sed is
> good enough. As in: there's a handful of case where that isn't the case.
> That's better than the reverse and so far, not enough justification to
> change anything.

Problems with security/gnome-keyring and www/webkit-gtk come to mind.

The major headache was that its wasn't behaving as expected, I had tested
and knew that the expression didn't work with nbsed but did with gsed, so
I couldn't understand why add gsed to USE_TOOLS didn't work.

If gsed is not going to be treated specially then what should be done in
those handful of cases?

Should we get rid of all 'gsed' references from USE_TOOLS?  

-- 
Steven