From: "Ludovic Courtès" <ludo@gnu.org>
To: Guix-devel <guix-devel@gnu.org>
Subject: Guile 3 migration plan
Date: Thu, 16 Jan 2020 11:08:15 +0100 [thread overview]
Message-ID: <874kwvemsw.fsf@inria.fr> (raw)
Hello Guix!
Today is Guile 3 day, a day to celebrate, woohoo! \o/
How will Guix migrate to Guile 3? That’s a threefold process:
1. We must first migrate packages. I propose to rename “guile-next”
to “guile” today, such that “guix install guile” will now install
Guile 3 (no mass rebuild involved: the “default” Guile remains
2.2.)
The downside is that if you run “guix install guile guile-json”,
you’ll get Guile 3 with Guile-JSON for 2.2; instead, you have to
explicitly select “guile3.0-json”.
I propose renaming all the “guile3.0-” packages to “guile-”, and
all the “guile-” packages to “guile2.2-” as a second step, which
will address this issue. This could be done within a few days or
weeks.
2. We must be able to run Guix itself on Guile 3. This is already
possible if you add “3.0” to the ‘GUILE_PKG’ invocation in
‘configure.ac’, but there are still a few test failures that I’ve
been working on. Almost all of them relate to the use of ‘@@’ and
‘mock’, which do not work with Guile 3 “declarative modules”.
In many cases, it’s an opportunity to clean up our tests; see for
example 4aea90b1876179aab8d603a42533a6bdf97ccd3c and the preceding
commit. It should be possible to be done real soon!
Once we’re done, we can change (guix self) so that ‘guix pull’
pulls Guix on Guile 3.
3. Change ‘default-guile’ to point to Guile 3 in ‘core-updates’, and
switch all the packages that consume .go files coming from
‘with-imported-modules’ to Guile 3, in particular ‘shepherd’ and
‘mcron’.
Thoughts?
You can celebrate Guile 3 day by helping out any of these! Let’s
synchronize here and on IRC! :-)
Ludo.’
next reply other threads:[~2020-01-16 10:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 10:08 Ludovic Courtès [this message]
2020-01-16 13:57 ` Guile 3 migration plan zimoun
2020-01-16 14:57 ` Efraim Flashner
2020-01-16 17:23 ` Ludovic Courtès
2020-01-16 17:58 ` Vagrant Cascadian
2020-01-17 21:43 ` Ludovic Courtès
2020-01-17 21:48 ` Ludovic Courtès
2020-01-19 21:29 ` Ludovic Courtès
2020-01-20 17:11 ` Ludovic Courtès
2020-01-23 16:39 ` Ludovic Courtès
2020-01-23 22:25 ` Ricardo Wurmus
2020-01-24 9:29 ` Ludovic Courtès
2020-01-25 17:37 ` Ludovic Courtès
2020-01-25 19:03 ` Ricardo Wurmus
2020-01-28 10:26 ` Ludovic Courtès
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=874kwvemsw.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=guix-devel@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 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.