Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file name we could
have icedtea-1.2:1.6.ebuildN and icedtea-1.2:1.7.ebuildN. This
particular situation
On Fri, 12 Sep 2008 21:12:30 +0300
Petteri Räty [EMAIL PROTECTED] wrote:
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file name we
could have
On 14:56 Fri 12 Sep , Doug Goldstein wrote:
Petteri Räty wrote:
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file name we could
have
Donnie Berkholz kirjoitti:
On 14:56 Fri 12 Sep , Doug Goldstein wrote:
Petteri Räty wrote:
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file
On 22:21 Fri 12 Sep , Petteri Räty wrote:
I do know how to get around it, I did state that in my original email.
As it happens we are having a discussion on gentoo-java mailing list on
whether we should use icedtea-openjdk build.icedtea version.ebuild
or have different packages for
Donnie Berkholz kirjoitti:
On 22:21 Fri 12 Sep , Petteri Räty wrote:
I do know how to get around it, I did state that in my original email.
As it happens we are having a discussion on gentoo-java mailing list on
whether we should use icedtea-openjdk build.icedtea version.ebuild
or have