Gentoo Archives: gentoo-dev

From: Aaron Walker <ka0ttic@g.o>
To: gentoo-dev@××××××××××××.org
Subject: Re: [gentoo-dev] perl, sed and non-gsed
Date: Tue, 29 Mar 2005 14:16:06
Message-Id: 4248E07E.9040400@gentoo.org
In Reply to: Re: [gentoo-dev] perl, sed and non-gsed by Ciaran McCreesh
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Ciaran McCreesh wrote:
5 > On Mon, 28 Mar 2005 18:06:17 +0200 "Diego \"Flameeyes\" Petten�"
6 > <flameeyes@×××××××××××××.de> wrote:
7 > | Please also note that using a sintax like that:
8 > |
9 > | sed -e expression file file file -i
10 > |
11 > | just works on gsed, but doesn't work with other sed implementations
12 > | (bsdish, macos, solaris, ...). -i must be put before any -e!
13 > |
14 > | Please update the erroneous ebuild, as these could make problems when
15 > | gentoo/non-linux-os .
16 >
17 > Erm. No. Supporting -i is a requirement for any sed that is used by
18 > ebuilds. If your native sed doesn't do it, you must provide a sed alias
19 > to, say, GNU sed when in an ebuild environment. We already went over
20 > that with the osx thing. Switching is infeasible.
21 >
22 > Historically, any ebuild using sed -i would have a hard DEPEND upon
23 > GNU sed-4. These were removed when GNU sed-4 became part of the
24 > profiles, but as they're system deps you should consider GNU sed 4 a
25 > requirement for your arch.
26 >
27
28 FYI Ciaran and Diego, sed is aliased to gsed on BSD.
29
30 - --
31 Reffreshed by a breeeff bleckuoot, I gut tu my feet und vent next duur.
32 Bork Bork Bork!
33 - -- Merteen Emees, _Muney_
34
35 Aaron Walker <ka0ttic@g.o>
36 [ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ]
37 -----BEGIN PGP SIGNATURE-----
38 Version: GnuPG v1.4.1 (GNU/Linux)
39
40 iD8DBQFCSOB9C3poscuANHARAiFfAJ9mluqYioRSFNAdYAnPZi58mYJcCQCeJBQN
41 iXr9KN6LWymB0WJ6KAmQN9E=
42 =2L+8
43 -----END PGP SIGNATURE-----
44
45
46 --
47 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] perl, sed and non-gsed "Diego \\\"Flameeyes\\\" Pettenò" <flameeyes@×××××××××××××.de>