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:
Created attachment 69994 [details, diff] Patched ebuild to do sed -i <file> -e <script> instead of sed -i -e <script> <file>
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
(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*.
Created attachment 70008 [details] emerge info (You won't like what you see!)
This problem is about more than just lazy ebuild writing or this one specific patch.
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`
appears to work for me.
This is a bootstrap issue. there is no gsed until `emerge system` is ran.
ah I didn't realise that.
(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!
(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?
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."
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?
Yegh! If Diego hasn't tackled this yet, then we for sure won't EVER do it.