The issue isn't that the syntax has to be sed -i -e <pattern> <file> not sed -e <pattern> -i <file>. Note that -i is supported it just MUST preceed any -e's.
--Dan On Mon, 2005-03-28 at 18:31 +0100, Ciaran McCreesh wrote: > On Mon, 28 Mar 2005 18:06:17 +0200 "Diego \"Flameeyes\" Petten�" > <[EMAIL PROTECTED]> wrote: > | Please also note that using a sintax like that: > | > | sed -e expression file file file -i > | > | just works on gsed, but doesn't work with other sed implementations > | (bsdish, macos, solaris, ...). -i must be put before any -e! > | > | Please update the erroneous ebuild, as these could make problems when > | gentoo/non-linux-os . > > Erm. No. Supporting -i is a requirement for any sed that is used by > ebuilds. If your native sed doesn't do it, you must provide a sed alias > to, say, GNU sed when in an ebuild environment. We already went over > that with the osx thing. Switching is infeasible. > > Historically, any ebuild using sed -i would have a hard DEPEND upon > GNU sed-4. These were removed when GNU sed-4 became part of the > profiles, but as they're system deps you should consider GNU sed 4 a > requirement for your arch. > -- [email protected] mailing list
