I moved my hardware in early october 2015 and therefore i had run several times emerge -e world ~amd64, openrc + eudev i fixed those errors during bootup with "runscript is deprecated, use bla bla instead" it seems some ebuilds in ~amd64 install deprecated config files, they were pulled in with etc-update. So i got this runscript is depreaced error again. solution a) support both solution b) fix those config files which preship with those packages. from the user point of view it is hard to say / causes issues usually to keep most of the unchanged files forever, so i usually only keep those which i changed and autoaccept those with etc-update which i believe i ever changed. that s why i get those runscript deprecated stuff. in the worst case scenario, the box could be unbootable soon. Reproducible: Always Could lead soon to unbootable boxes because the feature is depreacted. the fix i was told on forums.gentoo.org dates back to january 2015. So we can assume that next few version will cause many unbootable boxes, or boxes with some services which do not work. Workaround is to run this command as user root in the folder (But i do not get the point to run this line on every usage of portage! sed -i -- '1s/runscript/openrc-run/' /etc/init.d/*
Solution A you proposed above can't happen. The issue is that more than one package has a binary called runscript, so we are required to rename this one; that is why I named it openrc-run. Solution B will happen before runscript disappears, but this is not an issue internal to OpenRC. That is the only reason this bug is being marked invalid. Thanks, William