line 43: -ekeyword ~$ACCEPT_KEYWORDS $ebuild +ekeyword $ACCEPT_KEYWORDS $ebuild Reason: line 42[1] now returns ~x86-linux instead of x86-linux so ekeyword doesn't understand ~~x86-linux. [1]: source "${EPREFIX:-$(portageq envvar EPREFIX)}"/etc/make.profile/make.defaults
could you try out revision 15087?
(In reply to comment #1) > could you try out revision 15087? % source "${EPREFIX:-$(portageq envvar EPREFIX)}"/etc/make.profile/make.defaults % echo "~${ACCEPT_KEYWORDS#~}" #r15087 ~~x86-linux % echo "${ACCEPT_KEYWORDS#~}" # I think this is what you want ~x86-linux I think you want the last one, yes? Not the first one because that creates a double ~~ which ekeyword doesn't understand.
did you try it? We still want ~arch keywords. ${ACCEPT_KEYWORDS#~} means strip off a leading ~ if any, unless I screwed it up ;) I wasn't sure, so backwards_compatibility++
(In reply to comment #3) > did you try it? Of course, still failed. > We still want ~arch keywords. Obviously. > ${ACCEPT_KEYWORDS#~} means strip off a leading ~ if any, unless I screwed it up You screwed it up. I'm not sure of the bash expansion needed here but what you provided doesn't strip off the leading ~, it just doesn't expand to a single ~. IF ACCEPT_KEYWORDS=~ then "~${ACCEPT_KEYWORDS#~}" prints a lone ~ because a ~ is in front of the $. "${ACCEPT_KEYWORDS#~}" prints nothing. Try it out.
I the h@ck screwed it up indeed ///1P!LL Try out 15088 (tested this time)
(In reply to comment #5) > I the h@ck screwed it up indeed ///1P!LL > > Try out 15088 > > (tested this time) Yup, looks good this time. Works too =) Question: Will the profile ever set ACCEPT_KEYWORDS to be '~' - I'm am unclear why it can't just be $ACCEPT_KEYWORDS and forget about stripping the leading ~ then adding it back.
I only yesterday changed all profiles, so technically it shouldn't be necessary, but people tend to have the most weird setups, so in order not to break...
