1 |
On Mon, 10 Nov 2014 12:23:43 +0100 |
2 |
Pacho Ramos <pacho@g.o> wrote: |
3 |
|
4 |
> Hello |
5 |
|
6 |
Hello, this is an individual response. |
7 |
|
8 |
> I would like to see if we could finally try to stabilize java7 on |
9 |
> Gentoo as some external tools start to require it. |
10 |
> |
11 |
> There is currently this tracker opened: |
12 |
> https://bugs.gentoo.org/show_bug.cgi?id=384609 |
13 |
> |
14 |
> I am unsure why: |
15 |
> https://bugs.gentoo.org/show_bug.cgi?id=483018 |
16 |
> |
17 |
> should block the stabilization as we can have multiple java versions |
18 |
> installed due slots |
19 |
|
20 |
Multiple stable Java versions means more work; so, you'll instead want |
21 |
to bring incompatible packages forward to Java 7 or mask and lastrite |
22 |
them as time goes by. |
23 |
|
24 |
> The tracker list two broken packages that would need either patching |
25 |
> or to be forced to use older slots and this one: |
26 |
|
27 |
Under the work train of thoughts, an older slot is a temporary measure. |
28 |
|
29 |
> https://bugs.gentoo.org/show_bug.cgi?id=515830 |
30 |
> |
31 |
> That looks more important. Then, I also wonder about what |
32 |
> implementations are we meant to look for this stabilization. Should we |
33 |
> look for bugs affecting icedtea-bin and also oracle's implementation? |
34 |
|
35 |
If you look at the history, multiple implementations are stabilized; |
36 |
this means that bugs should indeed look at whether they affect both |
37 |
versions. In general, fixing a bug for one implementation fixes it for |
38 |
the other implementation or the other implement didn't even have the |
39 |
bug to begin with; but that shouldn't fool us to check them both out. |
40 |
|
41 |
> (I was wondering if the tracker was really collecting all the |
42 |
> issues :/) |
43 |
|
44 |
Doubtful. A tree wide check is necessary to confirm that all Java based |
45 |
packages build with the to be stabilized Java 7 implementations. |