1 |
Joshua Nichols wrote: |
2 |
> You forgot to attach the patch :) |
3 |
> |
4 |
|
5 |
Damn :) Here it is. |
6 |
|
7 |
> But it's moot, since I just barely fixed it before seeing your message. |
8 |
>> But then I've run into another problem. It allows root to set user-vm as |
9 |
>> well as system-vm, while java-config-2 doesn't. java-config-2 then lists |
10 |
>> it as active with java-config -L (probably causes other problems too). |
11 |
>> There's no way to unset it but removing /root/.gentoo/java-config-2 |
12 |
>> So, eselect java shouldn't list or allow changing of user-vm for root. |
13 |
>> Haven't tried to fix that. |
14 |
>> |
15 |
>> |
16 |
> Right you are. It should die now if you try to set a user vm as root. |
17 |
> |
18 |
> On a related note, it seems that the eselect module sets stuff by hand, |
19 |
> ie by creating symlinks and whatnot. I'm not sure if this was |
20 |
> intentional, or if it should be using java-config to do this instead. |
21 |
> |
22 |
|
23 |
Using java-config to set stuff would be easy. To list stuff, it would |
24 |
need to parse its output. I'm not even sure if an user can determine |
25 |
system-vm with java-config. Maybe use the python functions that |
26 |
java-config uses? |
27 |
|
28 |
> In any event, thanks for the report. This is exactly the stuff I want to |
29 |
> be found and fixed before we merge the migration-overlay into the main |
30 |
> tree. |
31 |
> |
32 |
|
33 |
Glad to help :) |
34 |
|
35 |
Caster |