From: Timothy Sample <samplet@ngyro.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Building Bash with Geesh
Date: Fri, 07 Dec 2018 19:33:18 -0500 [thread overview]
Message-ID: <87lg50x3g1.fsf@ngyro.com> (raw)
In-Reply-To: <87sgz9asgr.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 07 Dec 2018 23:21:24 +0100")
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> ...
>
> Which parts of 2.2 that 2.0 lacks does it need? PEG?
For Geesh, I think it is mostly just trivialities like “peek-char”
vs. “lookahead-char”. I started adapting it once, and fixing one or two
small things like that would make the front-end (lexer and parser) work
for Guile 2.0. I’m less sure about the back-end. Being relatively new
to Guile means that Guile 2.2 just *is* Guile as far as I know. :)
> Overall I’m in favor of changing the bootstrap seeds as rarely as
> possible. Also, if our horizon is a full Scheme bootstrap has Jan
> proposed (and I think that’s a great plan!), then perhaps we’ll have to
> arrange to not rely on fancy Guile features in build-side code meant to
> run early on during bootstrap. So far it was easy to keep (guix build …)
> valid for both 2.2 and 2.0, but these are simple modules; I don’t know
> whether that’s reasonably feasible for more complex pieces of software
> like Geesh and Gash.
>
> All that said, the benefit of removing Bash from the seeds may well
> outweigh the “cost” of upgrading to Guile 2.2.
This makes sense. I’m pretty sure we could stick with version 2.0 if
we’re careful.
> ...
>
> It’d be great if both projects could converge; there’ll still be plenty
> of challenges to satisfy your playfulness anyway. :-) (Like, say, a
> shell→tree-il front-end, hint hint ;-)).
Agreed! Imagining a “(language shell spec)” module was what got me
motivated in the first place. :)
> That said I can imagine it’s not that easy and maybe also less fun but
> it would help the longer-term goal of building a solid foundation for
> bootstrapped distros.
>
> Anyway, kudos on these achievements! I guess we at least need Geesh and
> Gash packages now! :-)
Forthcoming!
> Ludo’.
-- Tim
next prev parent reply other threads:[~2018-12-08 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 15:44 Building Bash with Geesh Timothy Sample
2018-12-07 17:08 ` Jan Nieuwenhuizen
2018-12-07 22:21 ` Ludovic Courtès
2018-12-08 0:33 ` Timothy Sample [this message]
2018-12-08 6:47 ` Jan Nieuwenhuizen
2018-12-08 1:01 ` Timothy Sample
2018-12-09 4:17 ` Chris Marusich
2018-12-09 6:58 ` Jan Nieuwenhuizen
2018-12-09 15:20 ` Timothy Sample
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lg50x3g1.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).