| 1 |
The issue isn't that the syntax has to be sed -i -e <pattern> <file> not |
| 2 |
sed -e <pattern> -i <file>. Note that -i is supported it just MUST |
| 3 |
preceed any -e's. |
| 4 |
|
| 5 |
--Dan |
| 6 |
|
| 7 |
On Mon, 2005-03-28 at 18:31 +0100, Ciaran McCreesh wrote: |
| 8 |
> On Mon, 28 Mar 2005 18:06:17 +0200 "Diego \"Flameeyes\" Pettenò" |
| 9 |
> <flameeyes@×××××××××××××.de> wrote: |
| 10 |
> | Please also note that using a sintax like that: |
| 11 |
> | |
| 12 |
> | sed -e expression file file file -i |
| 13 |
> | |
| 14 |
> | just works on gsed, but doesn't work with other sed implementations |
| 15 |
> | (bsdish, macos, solaris, ...). -i must be put before any -e! |
| 16 |
> | |
| 17 |
> | Please update the erroneous ebuild, as these could make problems when |
| 18 |
> | gentoo/non-linux-os . |
| 19 |
> |
| 20 |
> Erm. No. Supporting -i is a requirement for any sed that is used by |
| 21 |
> ebuilds. If your native sed doesn't do it, you must provide a sed alias |
| 22 |
> to, say, GNU sed when in an ebuild environment. We already went over |
| 23 |
> that with the osx thing. Switching is infeasible. |
| 24 |
> |
| 25 |
> Historically, any ebuild using sed -i would have a hard DEPEND upon |
| 26 |
> GNU sed-4. These were removed when GNU sed-4 became part of the |
| 27 |
> profiles, but as they're system deps you should consider GNU sed 4 a |
| 28 |
> requirement for your arch. |
| 29 |
> |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives