I have FEATURES=nodoc and global USE=-doc, but I set local USE=doc on sun-jdk in order to pull in the documentation, java-sdk-docs. In this configuration, the whole contents of the package (to be installed under /usr/share/doc) are deleted from the image prior to install. Surely there is no sense in permitting this to happen. I imagine, if one looked, there might be other standalone documentation ebuilds that would be similarly affected. I believe this ebuild should either ignore/override/work around FEATURES="nodoc" (if this is possible to do), or install to a different directory to avoid being zapped. Reproducible: Always
Not much we Java folks can do about so reassigning to Portage people. The only thing that comes to mind is using /etc/portage/bashrc to disable nodoc for certain ebuilds.
Something like this in /etc/portage/bashrc should do it: [[ ${PN} == java-sdk-docs ]] && export FEATURES=${FEATURES/nodoc}
Dupe of bug #44796 as far as I'm concernced.
*** This bug has been marked as a duplicate of bug 44796 ***