Since more browsers than mozilla can use the java browserplugin , we should probably rename the useflag. The current situation: A user (let's say one who hasnt a jdk/jre installed) merges mozilla-firefox with USE="java" and expects that he can see java applets on websites. The java useflag controlls a rdepend on virtual/jre which is getting installed. In this case where the user has no jdk/jre installed it will probably install the blackdown-jre. The blackdown-jre only installs the browserplugin if the mozilla useflag is enabled. Many users dont know this, and it's not a very clean solution. The idea: We could rename both useflags, mozilla's java useflag and the mozilla useflag of jdks/jres, to something which has the same name like "javaplugin". If somebody now does the following...: USE="javaplugin" emerge mozilla-firefox ...the blackdown-jre will also be installed, but since the blackdown-jre uses the same useflag to control wether the plugin should be made available or not it will install it. That makes much more sense than the current situation where you have to use two useflags to install the java-plugin: USE="mozilla java" emerge mozilla-firefox Most of the users arent aware of that fact, and it avoids that somebody has to merge the jre twice. The useflag can be changed of course, was just an idea. What do you guys think?
i think its a good idea the mozilla ebuilds seem to have the java use flag, but don't use it, they always but the oji thing, so maybe java use can be removed there and have a "browserplugin" flag for the jdk/jre's
The pkg_postinst() function added to blackdown-jre ebuilds overrides the one specified in java.eclass. So, I think a call to java_pkg_postinst should be added to those ebuilds.
Thanks, fixed postinst
