From: "Ludovic Courtès" <ludo@gnu.org>
To: 74654@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#74654] [PATCH 0/5] Optimize 'all-packages'; add ungrafting manifest
Date: Mon, 2 Dec 2024 17:51:53 +0100 [thread overview]
Message-ID: <cover.1733158049.git.ludo@gnu.org> (raw)
Hello Guix!
This is a followup to <https://issues.guix.gnu.org/74542>:
• Optimizing ‘all-packages’ significantly (speeds up
‘guix build -P’ and ‘guix refresh -l’);
• Moving manifests to ‘etc/manifests’ (we’ll have to
update Cuirass specs that refer to these files);
• Adding an “ungrafting” package that rebuilds everything
without grafts, just like what we’d do manually.
The goal is to have that ungrafting manifest under CI, such
that anytime the corresponding jobset is green, we can ungraft
everything with the guarantee that binaries are available.
Thoughts?
Ludo’.
Ludovic Courtès (5):
etc: Move manifests to a separate directory.
packages: Optimize ‘all-packages’.
build-system/cargo: Simplify ‘crate-closure’.
guix build: Last argument of ‘dependents’ is optional.
maint: Add ungrafting manifest.
Makefile.am | 21 ++++----
.../disarchive.scm} | 2 +-
etc/{hurd-manifest.scm => manifests/hurd.scm} | 0
.../kernels.scm} | 0
.../release.scm} | 0
.../source.scm} | 0
etc/{ => manifests}/system-tests.scm | 0
.../time-travel.scm} | 0
etc/manifests/ungraft.scm | 49 +++++++++++++++++++
.../upgrade.scm} | 0
gnu/packages.scm | 30 +++++++-----
guix/build-system/cargo.scm | 12 ++---
guix/scripts/build.scm | 4 +-
13 files changed, 87 insertions(+), 31 deletions(-)
rename etc/{disarchive-manifest.scm => manifests/disarchive.scm} (99%)
rename etc/{hurd-manifest.scm => manifests/hurd.scm} (100%)
rename etc/{kernels-manifest.scm => manifests/kernels.scm} (100%)
rename etc/{release-manifest.scm => manifests/release.scm} (100%)
rename etc/{source-manifest.scm => manifests/source.scm} (100%)
rename etc/{ => manifests}/system-tests.scm (100%)
rename etc/{time-travel-manifest.scm => manifests/time-travel.scm} (100%)
create mode 100644 etc/manifests/ungraft.scm
rename etc/{upgrade-manifest.scm => manifests/upgrade.scm} (100%)
base-commit: 522732d5c15e44fc9e061f36a41f7129edfee66f
--
2.46.0
next reply other threads:[~2024-12-02 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 16:51 Ludovic Courtès [this message]
2024-12-02 16:53 ` [bug#74654] [PATCH 1/5] etc: Move manifests to a separate directory Ludovic Courtès
2024-12-03 3:05 ` Z572
2024-12-02 16:53 ` [bug#74654] [PATCH 2/5] packages: Optimize ‘all-packages’ Ludovic Courtès
2024-12-02 23:47 ` David Elsing
2024-12-02 16:53 ` [bug#74654] [PATCH 3/5] build-system/cargo: Simplify ‘crate-closure’ Ludovic Courtès
2024-12-02 19:11 ` Efraim Flashner
2024-12-02 22:24 ` Ludovic Courtès
2024-12-02 16:53 ` [bug#74654] [PATCH 4/5] guix build: Last argument of ‘dependents’ is optional Ludovic Courtès
2024-12-02 16:53 ` [bug#74654] [PATCH 5/5] maint: Add ungrafting manifest 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=cover.1733158049.git.ludo@gnu.org \
--to=ludo@gnu.org \
--cc=74654@debbugs.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).