Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 192699 - dev-java/java-sdk-docs installs nothing when FEATURES=nodoc
Summary: dev-java/java-sdk-docs installs nothing when FEATURES=nodoc
Status: RESOLVED DUPLICATE of bug 44796
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Ebuild Support (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-16 15:30 UTC by Robin Bankhead
Modified: 2007-09-17 02:33 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Bankhead 2007-09-16 15:30:58 UTC
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
Comment 1 Petteri Räty (RETIRED) gentoo-dev 2007-09-16 20:01:39 UTC
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.
Comment 2 Zac Medico gentoo-dev 2007-09-16 21:25:57 UTC
Something like this in /etc/portage/bashrc should do it:

[[ ${PN} == java-sdk-docs ]] && export FEATURES=${FEATURES/nodoc}
Comment 3 Marius Mauch (RETIRED) gentoo-dev 2007-09-17 01:09:08 UTC
Dupe of bug #44796 as far as I'm concernced.
Comment 4 Zac Medico gentoo-dev 2007-09-17 02:33:51 UTC

*** This bug has been marked as a duplicate of bug 44796 ***