1 |
> Actually, what I was asking was _would_ it work without the overlay? I |
2 |
> mean, if the ebuild is marked =virtual/jdk-1.4, then I could understand a |
3 |
> potential for trouble. But when it's just marked (whether by laziness or |
4 |
> whether it's correct) virtual/jdk, it'd be nice to know whether 1.5 could |
5 |
> work. |
6 |
|
7 |
No idea, how much the dependencies correspond with "would/wouldn't |
8 |
work". I wouldn't bet on that. The question, why would you so |
9 |
desperately try to have 1.5 JDK as (generation-1 without migration |
10 |
overlay) system vm? It can only break things, and gain you nothing. |
11 |
Somebody correct me if I'm wrong, but the bytecode compiled will be the |
12 |
same no matter which JDK you use. Any optimisations are done with |
13 |
run-time JIT compiling, and depends on the VM running the bytecode |
14 |
(which can be different from the VM used to compile). So, without |
15 |
migration overlay, you should best follow the java 1.5 faq, have 1.4 as |
16 |
sytem vm and use whatever vm as user vm. |
17 |
|
18 |
Caster |
19 |
-- |
20 |
gentoo-java@g.o mailing list |