From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>, Guix-devel <guix-devel@gnu.org>
Subject: Re: Guile 3 migration plan
Date: Thu, 16 Jan 2020 09:58:54 -0800 [thread overview]
Message-ID: <87pnfj8eqp.fsf@ponder> (raw)
In-Reply-To: <874kwvemsw.fsf@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On 2020-01-16, Ludovic Courtès wrote:
> Today is Guile 3 day, a day to celebrate, woohoo! \o/
Yay!
> How will Guix migrate to Guile 3? That’s a threefold process:
...
> 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.
...
> Once we’re done, we can change (guix self) so that ‘guix pull’
> pulls Guix on Guile 3.
Will it still be buildable from source with only guile 2.2? I have no
idea when Debian will have guile 3 available, for example, and was
hoping to be able to start the process of uploading ... "soon".
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-01-16 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 10:08 Guile 3 migration plan Ludovic Courtès
2020-01-16 13:57 ` zimoun
2020-01-16 14:57 ` Efraim Flashner
2020-01-16 17:23 ` Ludovic Courtès
2020-01-16 17:58 ` Vagrant Cascadian [this message]
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=87pnfj8eqp.fsf@ponder \
--to=vagrant@debian.org \
--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 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.