Per the policy, we ought to mask live ebuilds since the package contents is not stable [i.e. changes over time, can break randomly, etc.]. Since eclass-manpages generates data based on live contents, it is a live ebuild. Therefore, eclass-manpages should be keyword-masked. It would be also reasonable to reversion it to -9999* afterwards to indicate that it's not tied to a specific version of ::gentoo but always using the newest one.
commit 0e6856796a48e90ffe4ea97430b87ee4e708da58 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: Tue Mar 14 16:46:03 2017 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: Tue Mar 21 19:22:41 2017 app-portage/eclass-manpages: Clearly indicate the live ebuild, #612422 The current eclass-manpages ebuild uses the live tree to generate the manpages. The resulting manpages can therefore differ on each rebuild, and the ebuild can trigger broken output at random points in time depending on the current state of eclasses. Furthermore, the package contents randomly become stale and the user needs to rebuild it manually in order to obtain new contents. All this considered, the current ebuild is in essence a live ebuild. Following the policies for live ebuilds, rename it to version 9999* and remove all the keywords. Users wishing to use the live ebuild can unmask it per the policy.
