Deleting the usage tracker resulted in exceptions being silently
raised in a thread and this caused havoc with debuggers. Deleting the
hook that calls it instead is a smaller change and avoids both
problems.
It is possible that Oracle may use this hook for something else
later. I have therefore added a JAVA_PKG_STRICT check to display its
contents on each merge so that we can keep an eye on it.
See bug #559936 for more details.
Package-Manager: portage-2.2.20.1
mv "${WORKDIR}"/${JCE_DIR} lib/security/ || die
fi
- # Delete Oracle's evil usage tracker. Not just because it's evil but
- # because it breaks the sandbox during builds and we can't find any
- # other feasible way to disable it or make it write somewhere else.
- zip -d lib/rt.jar sun/usagetracker/\* || die
+ # Remove the hook that calls Oracle's evil usage tracker. Not just
+ # because it's evil but because it breaks the sandbox during builds
+ # and we can't find any other feasible way to disable it or make it
+ # write somewhere else. See bug #559936 for details.
+ zip -d lib/rt.jar sun/misc/PostVMInitHook.class || die
}
src_install() {