From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: IcedTea 1 / OpenJDK 6 discontinued
Date: Tue, 24 Jan 2017 23:04:18 +0100 [thread overview]
Message-ID: <87ziig3yjh.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170124191827.GA6311@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
Hi Leo,
Leo Famulari <leo@famulari.name> writes:
> Time marches on and IcedTea 1, which provides OpenJDK 6, is approaching
> the end of its life:
>
> http://blog.fuseyism.com/index.php/2017/01/11/discontinuation-of-support-for-icedtea-1-x/
>
> There will be one more release in the series, 1.14.0.
>
> Thankfully, we have zero packages that depend on it, except for
> icedtea-7, which inherits from it.
Thanks for the heads-up.
> What does everyone think we should do? I see 4 options:
>
> 1) Distributions like ours will have to support it ourselves. That means
> fixing bugs, including security issues. This would probably be a
> cross-distro effort.
>
> 2) We will continue to package it, but not try to support it. The
> package will be stuck in time, and we should mark it as deprecated
> somehow, at least with a comment in the package description.
>
> 3) We Will remove the package and adjust our icedtea-7 package to no
> longer inherit from icedtea-6.
>
> 4) Something else...
5) 2+3: Carry icedtea@6 until we have a reason to remove it (e.g.
security problems), but make sure it can go on short notice (no
inheritance).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-01-24 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 19:18 IcedTea 1 / OpenJDK 6 discontinued Leo Famulari
2017-01-24 22:04 ` Marius Bakke [this message]
2017-01-25 3:07 ` Kei Kebreau
2017-01-25 3:36 ` Leo Famulari
2017-01-25 9:04 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ziig3yjh.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.