From: Ricardo Wurmus <rekado@elephly.net>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: "classpath@gnu.org" <classpath@gnu.org>,
"Mark Wielaard" <mark@klomp.org>,
"Andrew Hughes" <gnu.andrew@redhat.com>,
Andïï <gnu_andrew@member.fsf.org>,
Andïï <gnu.andrew.rocks@gmail.com>,
"Andrew Haley" <aph@redhat.com>,
"Mario Torre" <neugens@redhat.com>,
java@gcc.gnu.org
Subject: Re: Status of GNU Classpath
Date: Fri, 10 Feb 2023 20:08:40 +0100 [thread overview]
Message-ID: <878rh549px.fsf@elephly.net> (raw)
In-Reply-To: <CABDcavb=oFFU7JLn6fW88hRzBu5QwGgHrGzXnwnaxOfMTf9eNA@mail.gmail.com>
Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com> writes:
> Would Guix be interested in new releases of GNU Classpath? Or are the
> current releases (0.93 + 0.99 + devel) "good enough" for what you
> need?
At this point there would likely be no benefit to Guix from a new
release of GNU Classpath, unless it would result in a shortening of the
bootstrap chain.
A new release that combines the properties (= build requirements and
supported target language version) of 0.93, 0.99, and the later devel
version would probably allow us to shorten the bootstrap some more. But
as it stands we’re happy with these historic releases as they serve us
well.
--
Ricardo
next prev parent reply other threads:[~2023-02-10 19:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABDcavY1sfVXs=zhF3fB+LS+HbszaDzs4KUzbkryFyz13ngtwQ@mail.gmail.com>
2023-02-06 12:55 ` Guillermo Rodriguez Garcia
2023-02-06 14:25 ` Ricardo Wurmus
2023-02-06 16:16 ` Guillermo Rodriguez Garcia
2023-02-08 10:42 ` Ricardo Wurmus
2023-02-08 15:55 ` Guillermo Rodriguez Garcia
2023-02-10 19:08 ` Ricardo Wurmus [this message]
2023-02-07 10:34 ` Andrew Haley
2023-02-07 10:55 ` Mark Wielaard
2023-02-07 10:47 ` Mark Wielaard
2023-02-07 13:00 ` Guillermo Rodriguez Garcia
2023-09-13 10:06 ` Guillermo Rodriguez Garcia
2023-09-14 8:15 ` Mark Wielaard
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=878rh549px.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=aph@redhat.com \
--cc=classpath@gnu.org \
--cc=gnu.andrew.rocks@gmail.com \
--cc=gnu.andrew@redhat.com \
--cc=gnu_andrew@member.fsf.org \
--cc=guille.rodriguez@gmail.com \
--cc=java@gcc.gnu.org \
--cc=mark@klomp.org \
--cc=neugens@redhat.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).