[gentoo-dev] Is it acceptable to use 'sed' in ebuild scripts?

[gentoo-dev] Is it acceptable to use 'sed' in ebuild scripts?

[Bob Phan]

Hello, I've just recently created an ebuild for nethack (put it in
app-games/nethack), however, it's build does not use the standard GNU
autoconf/automake system, but rather forces you to manually edit a config.h
file.  Currently, I have just made a patch for X support that is applied when
you "use X".  I would like to add Qt and GNOME optional support, but using
patches, it is very difficult to have one without the other, or the context
will not match (very messy).  I was instead wondering if using 'sed' within
ebuild scripts was accepted practice, or if I should stick a dependancy for
sed at the top of the file.

Thanks for any help.  I plan on writing a few more (hopefully more trivial)
ebuild scripts for any other software I run across.  Also, where should I
submit the ebuild after it's ready?

Thanks again,
Bob

PS. Great distro.  It's the first I have yet to use where I haven't
immediately found something I disliked, on top of its many other
merits.  Good work!

-- 
/*
 * Bob Phan <bob@evil-core.com,rphan@nrgn.com>
 * Computational Chemistry Informatics
 * Neurogen Corporation
 * (203)488-8201 x4645
 *
 * To understand recursion, you must first understand recursion.
 */

Re: [gentoo-dev] Is it acceptable to use 'sed' in ebuild scripts?

[Einar Karttunen]

On 05.02.02 07:41 -0500(+0000), Bob Phan wrote:
> Hello, I've just recently created an ebuild for nethack (put it in
> app-games/nethack), however, it's build does not use the standard GNU
> autoconf/automake system, but rather forces you to manually edit a config.h
> file.  Currently, I have just made a patch for X support that is applied when
> you "use X".  I would like to add Qt and GNOME optional support, but using
> patches, it is very difficult to have one without the other, or the context
> will not match (very messy).  I was instead wondering if using 'sed' within
> ebuild scripts was accepted practice, or if I should stick a dependancy for
> sed at the top of the file.

Yes, many ebuilds use sed
find /usr/portage/ -name '*ebuild' -exec grep -l 'sed -e' '{}' ';' 2>/dev/null|cut -d/ -f-5|uniq|wc -l
    300
So I don't think it will be banned in the near future.

> Thanks for any help.  I plan on writing a few more (hopefully more trivial)
> ebuild scripts for any other software I run across.  Also, where should I
> submit the ebuild after it's ready?

bugs.gentoo.org

- Einar Karttunen

Re: [gentoo-dev] Is it acceptable to use 'sed' in ebuild scripts?

[Tod M. Neidt]

On Tue, 2002-02-05 at 01:18, Einar Karttunen wrote:
> On 05.02.02 07:41 -0500(+0000), Bob Phan wrote:
> > Hello, I've just recently created an ebuild for nethack (put it in
> > app-games/nethack), however, it's build does not use the standard GNU
> > autoconf/automake system, but rather forces you to manually edit a config.h
> > file.  Currently, I have just made a patch for X support that is applied when
> > you "use X".  I would like to add Qt and GNOME optional support, but using
> > patches, it is very difficult to have one without the other, or the context
> > will not match (very messy).  I was instead wondering if using 'sed' within
> > ebuild scripts was accepted practice, or if I should stick a dependancy for
> > sed at the top of the file.
> 
> Yes, many ebuilds use sed
> find /usr/portage/ -name '*ebuild' -exec grep -l 'sed -e' '{}' ';' 2>/dev/null|cut -d/ -f-5|uniq|wc -l
>     300
> So I don't think it will be banned in the near future.
> 
As Einar said, many ebuilds use 'sed'.  A particularly good example that
you might want to take a look at is dev-lang/python-2.2-r4.

Hope that helps,

tod