From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Kyle Meyer" <kyle@kyleam.com>,
gwl-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: How to install GWL?
Date: Mon, 10 Feb 2020 01:22:56 +0100 [thread overview]
Message-ID: <CAJ3okZ0j3CMT0t9L1YXPi8sCXrJJX1L5M6pfHTBvh3r-0Y5_mQ@mail.gmail.com> (raw)
In-Reply-To: <877e10rflw.fsf@elephly.net>
Hi Ricardo,
On Wed, 5 Feb 2020 at 20:36, Ricardo Wurmus <rekado@elephly.net> wrote:
> Oh, I didn’t think of inferior number 1 at all, but that’s a good
> point. We could arrange for the build-time modules of Guix to be made
> available at runtime, independent of the version of Guix used to run
> “guix workflow”. Then we need to build packages with an inferior Guix,
> which is identical to the Guix used to run “guix workflow”.
Yes something along these lines.
Let restart the discussion after the new release.
I mean, the next release could still use the old mechanism because it
is more about the description language itself than the version of the
packages.
> (guix inferior) does not allow us to do this yet. The
> gexp->derivation-in-inferior procedure requires a derivation that
> returns some variant of Guix — we can’t just give it the directory name
> of the invoking command. I think this might be a good addition to (guix
> inferior).
Let open a discussion on guix-devel to collect some ideas. WDYT?
All the best,
simon
next prev parent reply other threads:[~2020-02-10 0:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 21:55 How to install GWL? Ricardo Wurmus
2020-01-23 1:15 ` Kyle Meyer
2020-01-23 10:06 ` Ricardo Wurmus
2020-02-01 9:26 ` Ricardo Wurmus
2020-02-05 14:34 ` zimoun
2020-02-05 19:36 ` Ricardo Wurmus
2020-02-10 0:22 ` zimoun [this message]
2020-01-23 1:17 ` zimoun
2020-01-23 11:14 ` Roel Janssen
2020-01-23 11:24 ` zimoun
2020-01-23 13:02 ` Ricardo Wurmus
2020-01-23 14:18 ` zimoun
2020-01-23 13:12 ` Ricardo Wurmus
2020-01-31 9:16 ` zimoun
2020-01-31 11:07 ` Ricardo Wurmus
2020-02-01 11:49 ` Ludovic Courtès
2020-02-05 13:50 ` zimoun
2020-02-05 13:46 ` zimoun
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=CAJ3okZ0j3CMT0t9L1YXPi8sCXrJJX1L5M6pfHTBvh3r-0Y5_mQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=ludo@gnu.org \
--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).