1 |
>> I was conviced, that ebuilds always use the lowest JDK version possible. |
2 |
>> But it seems, that packages use the System VM - which is 1.6 in my case. |
3 |
>> But 1.5 is also installed. |
4 |
> |
5 |
> Ebuilds compile source/target based on the lowest JDK version specified |
6 |
> in the ebuild. Which vm is used is controlled by by the ebuild and/or |
7 |
> the env. But most times that's restricted just to a version that |
8 |
> satisfied a virtual. Not specific vms. |
9 |
|
10 |
Oh good! I was hoping to hear that. |
11 |
|
12 |
But here, on my machine with default config, i'm compiling |
13 |
commons-daemon, and it says "using sun-jdk-1.6". |
14 |
Watch this: |
15 |
|
16 |
# emerge -1 commons-daemon |
17 |
Calculating dependencies... done! |
18 |
>>> Verifying ebuild Manifests... |
19 |
|
20 |
>>> Emerging (1 of 1) dev-java/commons-daemon-1.0.1-r2 to / |
21 |
* daemon-1.0.1.tar.gz RMD160 SHA1 SHA256 size ;-) ... |
22 |
|
23 |
[ ok ] |
24 |
* checking ebuild checksums ;-) ... |
25 |
|
26 |
[ ok ] |
27 |
* checking auxfile checksums ;-) ... |
28 |
|
29 |
[ ok ] |
30 |
* checking miscfile checksums ;-) ... |
31 |
|
32 |
[ ok ] |
33 |
* checking daemon-1.0.1.tar.gz ;-) ... |
34 |
|
35 |
[ ok ] |
36 |
* Using: sun-jdk-1.6 |
37 |
>>> Unpacking source... |
38 |
>>> Unpacking daemon-1.0.1.tar.gz to |
39 |
/var/tmp/portage/dev-java/commons-daemon-1.0.1-r2/work |
40 |
|
41 |
|
42 |
Oh, and even if i set the system VM to 1.5, it still uses sun-jdk-1.6. |
43 |
Strange! Look: |
44 |
|
45 |
# java-config -L |
46 |
The following VMs are available for generation-2: |
47 |
*) Sun JDK 1.5.0.13 [sun-jdk-1.5] |
48 |
2) Sun JDK 1.6.0.03 [sun-jdk-1.6] |
49 |
|
50 |
|
51 |
Why that? I don't find any particular line in commons-daemon's ebuild |
52 |
which specifies, that it should use JDK 1.6 instead of JDK 1.5. |
53 |
The dependencies are >=virtual/jdk-1.4 and such. |
54 |
|
55 |
|
56 |
Is this a bug, maybe? |