From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
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: Wed, 8 Feb 2023 16:55:57 +0100 [thread overview]
Message-ID: <CABDcavb=oFFU7JLn6fW88hRzBu5QwGgHrGzXnwnaxOfMTf9eNA@mail.gmail.com> (raw)
In-Reply-To: <87a61o5t4l.fsf@elephly.net>
El mié, 8 feb 2023 a las 11:50, Ricardo Wurmus (<rekado@elephly.net>) escribió:
> > Hi Ricardo,
> >
> >> > I can see that development halted around 2016 (from the commit logs of
> >> > the official git repo), but would like to know if someone else is
> >> > still using GNU Classpath.
> >>
> >> GNU Guix is using GNU Classpath in the bootstrap path from C to modern JDKs.
> […]
> > I understand that the above already does the job, and that GNU
> > Classpath is not used in Guix anymore once OpenJDK is built. Is this
> > correct?
>
> Classpath does not end up being used in applications at *runtime*, but
> it remains part of the bootstrap chain forever. In Guix we merely cache
> build artifacts, but the build inputs (instructions and the closure of
> all sources) are never fully divorced from the build outputs. In other
> words: we cannot ever *not* build Classpath if we want to build
> OpenJDK. Users only avoid building out the full bootstrap chain by
> downloading substitutes for a local build — but the builds themselves
> must happen somewhere (in this case on the build farm).
>
> We also rebuild the complete bootstrap chain whenever its inputs
> change. For Classpath and the OpenJDK this would happen, for example,
> when we use a new default C compiler, or any of the input libraries or
> tools change.
>
> We will need to continue to be able to build Classpath and all of the
> other early Java things for as long as Java packages should be buildable
> by Guix. Over the years this may require minor tweaks and patches.
Thank you Ricardo.
Given the specific needs of your use case I would like to ask the following:
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?
Thanks,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
next prev parent reply other threads:[~2023-02-08 15:56 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 [this message]
2023-02-10 19:08 ` Ricardo Wurmus
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='CABDcavb=oFFU7JLn6fW88hRzBu5QwGgHrGzXnwnaxOfMTf9eNA@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--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=java@gcc.gnu.org \
--cc=mark@klomp.org \
--cc=neugens@redhat.com \
--cc=rekado@elephly.net \
/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).