From: "Ludovic Courtès" <ludo@gnu.org>
To: Guix-devel <guix-devel@gnu.org>
Subject: Re: Will 2021 be the year of build systems on gexps?
Date: Wed, 10 Mar 2021 12:09:23 +0100 [thread overview]
Message-ID: <87eegn4658.fsf@gnu.org> (raw)
In-Reply-To: <87im6ojbbx.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 19 Feb 2021 17:01:38 +0100")
Hello!
Ludovic Courtès <ludo@gnu.org> skribis:
> Over the last few days I’ve been head-down working on
> ‘wip-build-systems-gexp’, the mythical branch that brings gexps to build
> systems and packages, so we can say goodbye to
> ‘build-expression->derivation’. And… it’s quite a ride!
The current tip of ‘wip-build-systems-gexp’ Just Works; it’s being built,
it can build ‘guix’ and cross-build things like ‘sed’:
https://data.guix-patches.cbaines.net/repository/2/branch/wip-build-systems-gexp
https://ci.guix.gnu.org/jobset/wip-build-systems-gexp (though Cuirass
currently has unrelated problems)
In terms of performance, there’s still a ~10% slowdown when computing
derivations compared to the ‘core-updates’ revision the branch is based
on.
Here’s what I’d like to do in the coming days, if that doesn’t interfere
with what others have in mind for the upcoming release:
• Monitor build failures due to typos/thinkos made while adjusting
build systems;
• Merge on ‘core-updates’.
Then there are optimizations to work on, but that can take a bit longer.
In particular, in ‘gexp->derivation’, allow file-like objects to be
specified as environment variable values. In turn, use that so that,
say, ‘gnu-build-system’ has a single builder for all its packages and
just calls ‘getenv’ to get the value of its various parameters, similar
to what (guix git-download) does.
That said, if people think it’s too late in the cycle, we could just as
well keep it for the next cycle.
Thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-03-10 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 16:01 Will 2021 be the year of build systems on gexps? Ludovic Courtès
2021-02-23 10:31 ` Rust packages and performance impact on Guix Ludovic Courtès
2021-02-23 14:28 ` Will 2021 be the year of build systems on gexps? Ludovic Courtès
2021-03-10 11:09 ` Ludovic Courtès [this message]
2021-03-10 11:15 ` Julien Lepiller
2021-03-10 14:12 ` zimoun
2021-03-10 17:00 ` Leo Famulari
2021-03-23 13:38 ` Ludovic Courtès
2021-03-23 16:08 ` Ricardo Wurmus
2021-03-30 2:16 ` Maxim Cournoyer
2021-03-30 21:38 ` Ludovic Courtès
2021-03-30 22:32 ` 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=87eegn4658.fsf@gnu.org \
--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 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).