Reading standard documentation I've find a little mistake:
man 5 ebuild:
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
$ 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:
See Also section of man 1 ebuild contains similiar issue (refers to /usr/sbin/ebuild.sh).
Thanks, fixed now:
This is fixed in 18.104.22.168 and 2.2.0_alpha170.
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:
This is fixed in 2.2.0.