Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 108282 - sys-devel/gettext-0.14.5.ebuild fails with no argument for BSD sed's -i option
Summary: sys-devel/gettext-0.14.5.ebuild fails with no argument for BSD sed's -i option
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Mac OSX (show other bugs)
Hardware: PPC OS X
: High normal (vote)
Assignee: Gentoo for Mac OS X
URL:
Whiteboard:
Keywords:
Depends on: 107759
Blocks:
  Show dependency tree
 
Reported: 2005-10-06 08:41 UTC by Jeroen Roovers (RETIRED)
Modified: 2007-03-26 19:11 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Patched ebuild to do sed -i <file> -e <script> instead of sed -i -e <script> <file> (gettext-0.14.5-sed-i.patch,815 bytes, patch)
2005-10-06 08:43 UTC, Jeroen Roovers (RETIRED)
Details | Diff
emerge info (You won't like what you see!) (emerge.info-macg3,1.57 KB, text/plain)
2005-10-06 11:26 UTC, Jeroen Roovers (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeroen Roovers (RETIRED) gentoo-dev 2005-10-06 08:41:23 UTC
sys-devel/gettext-0.14.5.ebuild (as well as sys-devel/gettext-0.14.4.ebuild) use 
sed in ways BSD's sed doesn't like. Patch for the ebuild coming soon. The 
problem arises because GNU sed is only merged after gettext.

Reproducible: Always
Steps to Reproduce:
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2005-10-06 08:43:34 UTC
Created attachment 69994 [details, diff]
Patched ebuild to do sed -i <file> -e <script> instead of sed -i -e <script> <file>
Comment 2 SpanKY gentoo-dev 2005-10-06 11:06:33 UTC
proposed patch isnt acceptable ... a hell of a lot more than just the gettext
ebuild uses this sort of 'lazy' syntax

in reality, the portage environment should be aliasing sed to gsed on BSD/OS X
which does support this syntax, so it sounds like your portage env is messed

no way to really know, you neglected to post `emerge info` like the bug report
page told you to
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2005-10-06 11:25:07 UTC
(In reply to comment #2)

> no way to really know, you neglected to post `emerge info` like the bug report
> page told you to

It didn't. In fact nothing or no one told me to submit this bug report/patch but 
*me*.
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2005-10-06 11:26:18 UTC
Created attachment 70008 [details]
emerge info (You won't like what you see!)
Comment 5 Jeroen Roovers (RETIRED) gentoo-dev 2005-10-06 11:27:21 UTC
This problem is about more than just lazy ebuild writing or this one specific 
patch.
Comment 6 Fabian Groffen gentoo-dev 2005-10-06 11:30:07 UTC
I see Panther.

profile.bashrc says:
[ -x /usr/bin/gsed ] && alias sed=gsed

so my question is, do you have gsed available on your system (you should have
somehow)

`which gsed`
Comment 7 Fabian Groffen gentoo-dev 2005-10-06 11:31:07 UTC
appears to work for me.
Comment 8 Kito (RETIRED) gentoo-dev 2005-10-06 11:32:43 UTC
This is a bootstrap issue. there is no gsed until `emerge system` is ran.
Comment 9 Fabian Groffen gentoo-dev 2005-10-06 11:36:00 UTC
ah I didn't realise that.
Comment 10 SpanKY gentoo-dev 2005-10-06 15:02:19 UTC
(In reply to comment #3)
> (In reply to comment #2)
>
> > no way to really know, you neglected to post `emerge info` like the bug
> > report page told you to
>
> It didn't. In fact nothing or no one told me to submit this bug report/patch
> but *me*.

it did actually ... from the Guided Enter A Bug page (in bold even):

Please paste all information from 'emerge info' in this section!
Comment 11 Jeroen Roovers (RETIRED) gentoo-dev 2005-10-06 15:16:17 UTC
(In reply to comment #10)

> it did actually ... from the Guided Enter A Bug page (in bold even):
> 
> Please paste all information from 'emerge info' in this section!

Note the difference between that and "like the bug report page told you to". 
Anyway, I still don't see how that could've possibly warranted closing the bug. 
Testing your reflexes?
Comment 12 Fabian Groffen gentoo-dev 2005-10-06 22:33:58 UTC
relax!  An emerge info output just gives insight in the environment settings for
portage.  It might not be evident that it's necessary, but sometimes it just
enables for recognition of certain patterns for example.

Please don't use the bug for flaming and that kind of useless time consuming
stuff.  "Ignorance is a bliss."
Comment 13 Nick Dimiduk (RETIRED) gentoo-dev 2006-02-07 10:12:02 UTC
Because GNU sed is required for use in ebuilds, I suggest the user emerge --nodeps sys-apps/sed before emerging system.  That'll get the ball rolling.  Once sed is installed, emerge --emptytree system will pull any of sed's dependencies along with it.  Has this bug otherwise gone stale?
Comment 14 Fabian Groffen gentoo-dev 2007-03-26 19:11:52 UTC
Yegh!  If Diego hasn't tackled this yet, then we for sure won't EVER do it.