Provided you are going to drop sun-java-bin I would you first to provide an equivalent of sun-jce-bin package. Thank you. See Bug #473830#c14 for more details.
Sorry, because I tried to keep things short on that bug I haven't yet answered on the JCE part in detail; the oracle-jdk-bin and oracle-jre-bin packages have the following USE flag that I think intends to deal with this: > <flag name="jce">Enable Java Cryptographic Extension Unlimited Strength Policy files</flag> Can you check whether that USE flag is sufficient? Since I'm fairly new I don't know of the history; so, I don't know if that USE flag covers what sun-jce-bin used to cover, but from the sound of it I guess that it does that. Thank you for testing that in advance.
Thanks, yes I haven't realized there is the USE=jce in the other java VM ebuilds. I even had set the USE=jce in my make.conf already. ;-) So, if the package.mask message explains that sun-jce-bin existing users should migrate to USE=jce and pick either of (oracle/icedtea VMs) I am fine with that: NO JCE SUPPORT 1) IBM JDK 1.6.0.9_p2 [ibm-jdk-bin-1.6] NO JCE SUPPORT 2) IBM JRE 1.6.0.9_p2 [ibm-jre-bin-1.6] WITH JCE SUPPORT 3) IcedTea JDK 7.2.4.1 [icedtea-7] WITH JCE SUPPORT 4) IcedTea JDK 6.1.12.6 [icedtea-bin-6] WITH JCE SUPPORT 5) IcedTea JDK 7.2.4.1 [icedtea-bin-7] WITH JCE SUPPORT *) Oracle JDK 1.7.0.40 [oracle-jdk-bin-1.7] WITH JCE SUPPORT 7) Oracle JRE 1.7.0.40 [oracle-jre-bin-1.7] WITH JCE SUPPORT 8) Sun JRE 1.6.0.45 [sun-jre-bin-1.6] The IBM java's don't respect USE=jce but maybe because they simply do not have that?
Hmm, actually the odd thing is that we do not mask sun-jce-bin; which makes me wonder, whether it should be made part of the mask. Given that it only works together with the masked packages, I guess so. I'll try to work it out further.
+# This is continued by Oracle Corproation, which has acquired Sun Microsystems +# in early 2010; as per http://en.wikipedia.org/wiki/Sun_acquisition_by_Oracle +# +# Users are suggested to upgrade to one of the newer Oracle packages like +# dev-java/oracle-jdk-bin or dev-java/oracle/jre-bin or choose another +# alternative we provide; eg. the IBM JDK/JRE or the open source IcedTea. +# +# Most of these packages provide a jce USE flag for those whom need the +# Java Cryptographic Extension Unlimited Strength Policy USE flag; whether that +# works depends from VM to VM, it seems to work for most except for the IBM VMs. +dev-java/sun-jce-bin While I'd prefer some way to list them, I don't see a clean way to do that for now; so, I've ended up with the above addition to the mask reason. + 14 Sep 2013; Tom Wijsman <TomWij@gentoo.org> package.mask: + Expand sun-* package.mask reason to explain continuation, alternatives and + also mask and explain JCE; as requested in bugs #473830 and bug #484680, + reported by Martin Mokrejš.
Great. So the answer for this bug should be: dev-java/oracle-jce-bin won't be created, the functionality is in Oracle java VMs and IcedTea VMs if installed with USE="jce". ;-)
