i have seen that you kinda provide support for seting the right context to newly emerged packages in ebuild.sh and it realy works for me. once I modify the path to setfiles in ebuild.sh, that is. is there some hidden reason why you made the file existance test fail? i ask this because i usualy forget to modify ebuild.sh on every server every time i emerge a new version of sys-apps/portage. Reproducible: Always Steps to Reproduce: 1. cat /usr/lib/portage/bin/ebuild.sh |grep "usr3/sbin" 2. 3.
Fixed in cvs for 49-r3. Due out momentarily.