Reading standard documentation I've find a little mistake: man 5 ebuild: ... FILES The /usr/sbin/ebuild.sh script. ... $ file /usr/sbin/ebuild.sh /usr/sbin/ebuild.sh: ERROR: cannot open `/usr/sbin/ebuild.sh' (No such file or directory) $ which ebuild /usr/bin/ebuild $ file /usr/bin/ebuild /usr/bin/ebuild: symbolic link to `../lib/portage/bin/ebuild' $ file /usr/lib/portage/bin/ebuild /usr/lib/portage/bin/ebuild: Python script, ASCII text executable I'm not resposible about the best way to fix it, but referring to an unexistent file is a bad thing.
Thanks, this is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d4a4a98f02f6a3eba2430a0a5659b7b5bdc44cc5
Ops. Excuse me. See Also section of man 1 ebuild contains similiar issue (refers to /usr/sbin/ebuild.sh).
Thanks, fixed now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c3c464acda75e0b93d33d447f419c4dbba058d00
This is fixed in 2.1.11.59 and 2.2.0_alpha170.
sys-apps/portage-2.1.11.62 Missed fix for translation (at least Russian). man 5 ebuild (translated) is OK. default (man 1) manual page (file /usr/share/man/ru/man1/ebuild.1.bz2) still contains outdated refer to non-existent file /usr/sbin/ebuild.sh.
(In reply to Sergey S. Starikoff from comment #5) > Missed fix for translation (at least Russian). Please file a new bug for Russian translations.
I was able to correct the Russian page myself, and also found one more in the English make.conf.5: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=b264a7aeb342ac8e2004a851aaa23e97a173de4d
This is fixed in 2.2.0.