Having java ebuilds pull in java-docs as a default (doc is fairly well default) is rather annoying. It forces portage to stop, stating that the package requires you to manually download the files. It should be there, but not included in RDEPEND. Reproducible: Always Steps to Reproduce:
AFAIK, java-docs are not included in RDEPEND on any sun-jdk ebuild. Also, they only will be depended if user has "doc" in his/her USE flags. Can you be little more specific on this carpaski ?
The issue wasn't that it could be disabled... it was that you couldn't do it without intervention... If I want extra docs, and I have that flag set, I might not expect to come back a few hours later to find out that it stopped because the docs have to be downloaded manually. I really don't like having packages cause portage to exit for optional functionality. USE="doc" shouldn't be a good enough reason to stop portage from executing. </twocents> I've added a 'F' to portage's pretend line to reference ebuilds like the java-sdk-docs one to let users know that there are fetch restrictions in place.
OK, i will put a fetch restrictions on dev-java/* that needs it. Hope to finish it before saturday. Thanks.
i have updated and commited dev-java/sun-jdk/*.ebuild to have RESTRICT="fetch", the next step is to add this to java-sdk-docs
OK, this was fixed and commited to portage tree.