public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lisa Seelye <lisa@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] sed vs gsed
Date: Wed, 25 Jan 2006 14:31:11 +0000	[thread overview]
Message-ID: <1138199471.7860.9.camel@localhost> (raw)
In-Reply-To: <200601250014.14116@enterprise.flameeyes.is-a-geek.org>

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

On Wed, 2006-01-25 at 00:14 +0100, Diego 'Flameeyes' Pettenò wrote:
> I think the time is mature to ask for another step of Gentoo/ALT 
> improvement ;)
> Currently ebuilds uses a sed syntax that's mostly GNU sed 4 compatible, but 
> incompatible with BSD sed for instance. This is usually fine as we aliases 
> sed to gsed in our bashrc so that the problem in sed calls is removed.
> The main problem happen with sed when called by xargs or by find, as that 
> ignores the aliases set in bashrc.
> What I'd like to ask is, if possible, to start using gsed instead, that's 
> present on both GNU and other userlands with current stable version of sed 
> (4.1.4; ppc-macos has no problem as the 4.0.9 version uses gsed anyway).
> 
> It might require to change the dependency over >=sys-apps/sed-4.1.4, but that 
> would help making portage a bit cleaner IMHO (instead of relying on sed being 
> the executable you need, it make sure you're using a GNU sed version) and 
> solves quite a few headaches for us.
> 
> Comments about this? (Please don't tell me to do a GLEP about this)

Can you change the PATH that Portage uses to do ebuilds to favour,
say, /usr/local/gentoo-bsd/wrappers/bin, first which will have a sed to
gsed wrapper?

-- 
Regards,
Lisa Seelye
GPG: 09CF5 2D6B8 2B72B 997A7 601BC B46B5 561E4 96FC5
http://www.thedoh.com/~lisa/site

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2006-01-25 14:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 23:14 [gentoo-dev] sed vs gsed Diego 'Flameeyes' Pettenò
2006-01-24 23:32 ` Mike Frysinger
2006-01-25  0:13   ` Diego 'Flameeyes' Pettenò
2006-01-25  0:29     ` Mike Frysinger
2006-01-24 23:48 ` Stephen Bennett
2006-01-25  0:17   ` Diego 'Flameeyes' Pettenò
2006-01-25  0:30     ` Mike Frysinger
2006-01-25  1:23     ` Ciaran McCreesh
2006-01-25  8:21       ` Diego 'Flameeyes' Pettenò
2006-01-25 13:26         ` Mike Frysinger
2006-01-26 10:43     ` Paul de Vrieze
2006-01-26 13:51       ` Mike Frysinger
2006-01-26 16:06         ` Paul de Vrieze
2006-01-26 18:53           ` Mike Frysinger
2006-01-27  8:17             ` Paul de Vrieze
2006-01-27 13:42               ` Mike Frysinger
2006-01-27 14:36                 ` Paul de Vrieze
2006-01-25  5:16 ` Georgi Georgiev
2006-01-25  5:47   ` Mike Frysinger
2006-01-25  8:19     ` Diego 'Flameeyes' Pettenò
2006-01-25  8:54       ` Grobian
2006-01-25  9:22         ` Diego 'Flameeyes' Pettenò
2006-01-26 10:47           ` Paul de Vrieze
2006-01-25 14:31 ` Lisa Seelye [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1138199471.7860.9.camel@localhost \
    --to=lisa@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox