If you use non-bash code (e.g. sed) in /etc/portage/bashrc, emerge claims you've used it in the ebuild (QA notice). To my understanding, this shouldn't happen as there's no reason to avoid external programs in bashrc. Reproducible: Always Steps to Reproduce: 1.Put non-bash code in /etc/portage/bashrc 2.Emerge something Actual Results: Emerge complains about the non-bash code Expected Results: No complaints.
hmm, we will need to know what portage version you are using as well. thanks.
Portage version is 2.2_rc8
If you're triggering that QA notice then it means you've called sed in global scope, which has performance implications and also suggests that you've called it at the wrong time. If you need to call sed then the call should either be conditional on the $EBUILD_PHASE or else use one of the phase hooks that are documented in the html docs if you install portage with USE=doc enabled. For example: if [ $EBUILD_PHASE = compile ] ; then sed ... fi or post_src_unpack() { sed ... }
