I’m pleased to announce that the new Java hotness has finally hit the tree 🙂 It’s currently in package.mask, but I expect to unmask it in the next few days.
To begin using it, you will need to add the appropriate entries to /etc/portage/package.unmask, and then follow the upgrade guide.
For those not familar with that this means, here are some highlights:
- Ability to switch the current VM on the fly
- Changes to the user and system VM take effect immediately, and no
longer are tied to the shell environment (ie no more running env-update &&
source /etc/profile after switching the sytem VM) - Now has the concept of a
Woohoo, finally – now I can stop installing all that Java crap manually and resume using portage. Thanks a bunch for the work.
The java-config-1 and java-config-2 seem a little complicated. Is this to support old ebuilds and new ebuild formats?
Is there a trend towards eselect? Would you want to make java-config a plugin for eselect, say eselect-java?
Thanks,
That is exactly what java-config-1 and java-config-2, to be able to support the old system while moving to the new system.
java-config itself does do a lot more than just selecting VM, so it wouldn’t directly and entirely convert into an eselect module. That being said, there _is_ a eselect module, java-vm, for selecting user and system VM.