html javadoc for java sdk
Created attachment 3101 [details] java-sdk-html-1.3.1.ebuild javadoc for java sdk 1.3.1
Created attachment 3102 [details] java-sdk-html-1.4.0.ebuild javadoc for java sdk 1.4.0
When (if?) this gets added to portage, since there is a 'doc' use var, maybe add a depend line (doc? app-doc/java-sdk-html) to at least sun's jdk to install this.
Good idea. Only problem I can see is that it relies on the "sun" license, which does not exist in /usr/portage/licenses. Please either attach the full license text to this bug, and name it appropriately (usually sun-<acronym from the top of the license file>), or see if it is actually any of the other licenses we have in /usr/portage/licenses (I sincerely doubt this to be the case). Apart from that, it looks okay (not sure if there's a point in rewriting the cp stuff in src_install to dohtml).
Created attachment 3135 [details] sun-j2sl The license doesn't seem to have an actual name, which is why I just said "sun" in the ebuilds. So, I'm naming it sun - Java 2 Specification License (sun-j2sl). Feel free to change it so something more appropriate if necessary.
The reason I did a cp loop instead of dohtml is that dohtml (and all the other 'do' commands) is recursive and there are quite a few subdirs. If there is a relatively easy way to change it dohtml, I don't mind doing it.
I meant above that the do commands are NOT recursive
dohtml -r turns on recursion, but it filters out all the .java files, so it's not really more practical to use in this case. Anyway, your packages have been committed, they are available as dev-java/java-sdk-docs-1.3.1 and dev-java/java-sdk-docs-1.4.0 I renamed them to be somewhat consistent with dev-python/python-docs :)
what about the doc? is sun-jdk? Should I submit an updated ebuild as a new bug?
You didn't change the license name in the ebuilds to sun-j2sl