From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Will 2021 be the year of build systems on gexps?
Date: Tue, 23 Mar 2021 17:08:41 +0100 [thread overview]
Message-ID: <87sg4lvomu.fsf@elephly.net> (raw)
In-Reply-To: <87wntyhtwc.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hello!
>
> Ludovic Courtès <ludo@gnu.org> skribis:
>
>> 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)
>
> It’s building and well!
Excellent! It’s great to see that you brought this idea across all
the hurdles you encountered in previous attempts. Inspiring!
>> 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’.
>
> I’ll go ahead with that if there are no objections.
This sounds reasonable to me. “core-updates” will need some work to
push it into shape for the next merge, but I don’t think merging a
well-monitored branch into “core-updates” would make the job
considerably harder.
Thank you!
--
Ricardo
next prev parent reply other threads:[~2021-03-23 17:07 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
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 [this message]
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=87sg4lvomu.fsf@elephly.net \
--to=rekado@elephly.net \
--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).