From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org
Cc: Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: branch master updated: ci: Add bootstrap packages to the core subset.
Date: Sat, 10 Jul 2021 12:17:30 +0200 [thread overview]
Message-ID: <878s2efp6t.fsf@gnu.org> (raw)
In-Reply-To: <20210709121221.22830.37147@vcs0.savannah.gnu.org> (guix-commits@gnu.org's message of "Fri, 09 Jul 2021 08:12:21 -0400")
Hi Mathieu!
guix-commits@gnu.org skribis:
> commit 37861f6c293d7ed1033050b2b0597885ba65186f
> Author: Mathieu Othacehe <othacehe@gnu.org>
> AuthorDate: Fri Jul 9 12:07:24 2021 +0200
>
> ci: Add bootstrap packages to the core subset.
>
> * gnu/ci.scm (%bootstrap-packages): New variable.
> (cuirass-jobs): Add it to the core subset.
[...]
> +(define %bootstrap-packages
> + ;; Return the list of bootstrap packages from the commencement module.
> + (filter package?
> + (module-map
> + (lambda (sym var)
> + (variable-ref var))
> + (resolve-module '(gnu packages commencement)))))
> +
> (define (packages-to-cross-build target)
> "Return the list of packages to cross-build for TARGET."
> ;; Don't cross-build the bootstrap tarballs for MinGW.
> @@ -508,7 +517,7 @@ valid."
> (map (lambda (package)
> (package-job store (job-name package)
> package system))
> - %core-packages)
> + (append %bootstrap-packages %core-packages))
I believe the effect is that the same-named packages, those not in
commencement.scm, are no longer being built, as discussed here:
https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00222.html
Should we arrange so that jobs for the commencement.scm packages get a
custom name, for example prefixed by “commencement.”?
Thanks,
Ludo’.
next parent reply other threads:[~2021-07-10 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210709121221.22830.37147@vcs0.savannah.gnu.org>
2021-07-10 10:17 ` Ludovic Courtès [this message]
2021-07-10 15:55 ` branch master updated: ci: Add bootstrap packages to the core subset Mathieu Othacehe
2021-07-25 20:00 ` 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
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=878s2efp6t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=othacehe@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).