ebuild modifies jvm
zip -d jre/lib/rt.jar sun/misc/PostVMInitHook.class || die
License clearly states:
You may not:
create, modify, or change the behavior of, classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun", “oracle” or similar convention as specified by Oracle in any naming convention designation.
this may mean legal trouble.
according to my research this may be no longer required.
previously it was breaking sandbox as jvm was trying to write files outside of sandbox.
I don't think that deleting a class would qualify as "create, modify, or change".
(In reply to Georgy Yakovlev from comment #0)
The ebuild has "Oracle-BCLA-JavaSE" (corresponding to https://www.oracle.com/downloads/licenses/binary-code-license.html). Is that no longer accurate?
summary of IRC discussion:
oracle-jdk-1.8 versions <=220.127.116.11 seem still to be under Oracle-BCLA-JavaSE
oracle-jdk-1.8 >=1.8.222 are under new license (we don't have those in tree as of now)
>=oracle-jdk-11 seem to be under new license, but I can't reliably verify.
as for class deletion, usage tracker seems to be disabled by default with recent versions, so probably it's better to delete the hack. I could not reproduce sandbox faulures with 18.104.22.168 and class removal line deleted from ebuild.