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