From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Kyle Meyer <kyle@kyleam.com>, gwl-devel@gnu.org
Subject: Re: Next steps for the GWL
Date: Thu, 6 Jun 2019 13:59:51 +0200 [thread overview]
Message-ID: <87o93akjpk.fsf@mdc-berlin.de> (raw)
In-Reply-To: <CAJ3okZ2GnXfcaEDtC8vJmC6+Zu2jehJ3MB8B3i9Ex3gqJasmfQ@mail.gmail.com>
Hi simon,
> I agree that the mechanism such as `git-annex` should be nice.
> But is it not a mean for the CAS that we previously discussed?
I does not need to be the *only* mechanism. Multiple backends can serve
different users.
> I fully agree with the features and their description. Totally cool!
> However, I am a bit reluctant with `git-annex` because it requires a
> Haskell compiler and it is far far from "bootstrapability". I am aware
> of the Ricardo's try---and AFIAK the only one. And here [1]
> explanations by one Haskeller.
This is off-topic, but I’m probably going to bite the bullet and simply
use GCC 2.x to build an old GHC 4.x from the C “source” files, which are
surprisingly close to actual source code. I’ve tried to build GHC 4.x
with a recent compiler, but the code depends on too many quirks of GCC 2
that make it very hard to be sure about the behavior post migration.
(Re [1]: I talked to Joachim at one of the repro builds summit about the
GHC bootstrapping attempts, which prompted their blog post.)
--
Ricardo
next prev parent reply other threads:[~2019-06-06 11:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 13:47 Next steps for the GWL Ricardo Wurmus
2019-06-03 15:16 ` zimoun
2019-06-03 16:18 ` Ricardo Wurmus
2019-06-06 11:07 ` zimoun
2019-06-06 12:19 ` Ricardo Wurmus
2019-06-06 13:23 ` Pjotr Prins
2019-06-06 3:19 ` Kyle Meyer
2019-06-06 10:11 ` Ricardo Wurmus
2019-06-06 10:55 ` zimoun
2019-06-06 11:59 ` Ricardo Wurmus [this message]
2019-06-06 13:44 ` Pjotr Prins
2019-06-06 14:06 ` Pjotr Prins
2019-06-06 15:07 ` Kyle Meyer
2019-06-06 20:29 ` Ricardo Wurmus
2019-06-07 4:11 ` Kyle Meyer
2019-06-12 9:46 ` 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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o93akjpk.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=gwl-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=zimon.toutoune@gmail.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).