[arch-dev-public] Fwd: [arch-general] Java 8
guillaume at alaux.net
Sun Mar 30 08:47:11 EDT 2014
On 30 March 2014 14:23, Allan McRae <allan at archlinux.org> wrote:
> On 30/03/14 21:36, Guillaume Alaux wrote:
>> On 30 March 2014 11:46, Andreas Radke <andyrtr at archlinux.org> wrote:
>>> Am Sun, 30 Mar 2014 11:21:25 +0200
>>> schrieb Guillaume ALAUX <guillaume at archlinux.org>:
>>>> Hi devs,
>>>> A new major version of Java went out recently : "OpenJDK 8" but we
>>>> do not have a package for it (for the following reason) and some
>>>> Archers are asking questions  or flagging our openjdk7 package as
>>>> out of date:
>>>> All Linux distros - including Arch - build OpenJDK using the IcedTea
>>>> project . Its goal is to cleanly build OpenJDK from Oracle, bring
>>>> some more feature and it **was** also to re-implement closed source
>>>> parts. I expected IcedTea to quickly release a version for OpenJDK8
>>>> but it seems this is not their first priority  (which I totally
>>>> understand). Nowadays there is no closed source part anymore in
>>>> OpenJDK, and the license is clearly "GPL with classpath exception"
>>>> which is a standard in the Java world.
>>>> I have been working on a package based on OpenJDK8 built from source
>>>> but without IcedTea that I think would fit to our repos. I still have
>>>> some work for it to be released but I would be in favor of pushing
>>>> this "OpenJDK without IcedTea" to extra until IcedTea v3.0 stable is
>>>> out and could be used to build/augment our package.
>>>> Any thought/objection/remark about?
>>> How about using icedtea master bzr shots to build openjdk8 until they
>>> publish a release?
>> I should have mentionned: I tried that. It turns out the last
>> pre-release of IcedTea points at source tarballs (hotspot, jaxp,
>> corba, ...) that are not available anymore. One solution there could be
>> to get in touch with IcedTea and ask them to put these tarballs back
>> or create a new pre-release. Or to create our own tarballs. This
>> should not be too long to get all this to build.
> You can just use the bzr source directly in the PKGBUILD, even providing
> a revision for consistent builds.
Yes. Downside is: Each IcedTea minor version requires a set of source
tarballs of several components (jdk, corba, jaxp, ...) each at a precise
mercurial changeset. These are not available anymore. I could pull
each mercurial repo (5 repos AFAIK), create each tarball and make them
available on ftp.
So that would make a "pre-release" version of OpenJDK+IcedTea in our
repos. Would this be pushed to testing or extra? Are we in favor of
this compared to a "General Availability" vanilla OpenJDK?
More information about the arch-dev-public