| Summary: | support for per user settings for eseelect java-nsplugin | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Guilherme Barile <gui> |
| Component: | New packages | Assignee: | Java team <java> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Guilherme Barile
2006-07-10 10:56:43 UTC
It really isn't possible (afaik) to have the system's java plugin be changed along with the system vm. This is because the plugin is a file that lives in /usr/lib/nsbrowser/plugins/java-plugin.so. This used to be copied here if you emerge a jdk/jre with USE=nsplugin, but was recently changed because it causes file collisions when you emerge more than one. You also can't have this point at something under /etc/java-config-2/current-system-vm because plugins could feasibly be at different file names, or not even be available . So instead, we have an eselect module, java-nsplugin, to manage the current system java plugin. It doesn't currently let you define a per user plugin, because I think it's a bit trickier to manage than the system one. shouldn't the plugin be set when you set the system-vm then ? maybe the jdk/jre ebuilds should create a link to its plugin in JAVA_HOME/plugin.so, and the plugin on /usr/lib/mozilla should link to current_vm/plugin.so I don't think it's a problem (at least for firefox) if the link is dead, so, it wouldn't be a problem if the current vm doesn't provide a plugin at all (is there any vm that doesn't provide a plugin anyway?) Sun doesn't provide one for amd64. Kaffe doesn't provide one. Jrockit doesn't provide one. I'm pretty sure the way it is now is slighty better than your suggestion, because the java plugin should always work, regardless of what your system vm is. Perhaps it may make sense that, if the system vm has a plugin installed, it might set the system nsplugin too. That might be a little tricky to implement though with the way things are atm. If you have two users, and system-vm is 1.4 User1 vm is 1.4 User2 vm is 1.5 If you set java-plugin to 1.4, it won't work for User2. If you set the java-plugin to 1.5, it won't work for User1. |
