From: "Ludovic Courtès" <ludo@gnu.org>
To: 62047@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Christopher Baines" <mail@cbaines.net>,
"Josselin Poiret" <dev@jpoiret.xyz>,
"Ludovic Courtès" <ludo@gnu.org>,
"Mathieu Othacehe" <othacehe@gnu.org>,
"Ricardo Wurmus" <rekado@elephly.net>,
"Simon Tournier" <zimon.toutoune@gmail.com>,
"Tobias Geerinckx-Rice" <me@tobias.gr>
Subject: [bug#62047] [PATCH 0/2] '--with-input' & co. no longer replace hidden packages
Date: Wed, 8 Mar 2023 13:01:25 +0100 [thread overview]
Message-ID: <20230308120125.17560-1-ludo@gnu.org> (raw)
Hello,
This change makes things like:
guix build --with-input=guile=guile-next guix -n --no-grafts
more useful and tractable.
Low-level rewrites are still possible for packages not marked
as hidden in 'commencement.scm', such as glibc:
guix build --with-latest=glibc hello -n
Thoughts?
Ludo'.
Ludovic Courtès (2):
packages: Use SRFI-71 instead of SRFI-11.
packages: 'package-input-rewriting/spec' ignores hidden packages.
doc/guix.texi | 21 ++++++++++++---------
guix/packages.scm | 14 ++++++++------
tests/packages.scm | 20 +++++++++++++++++++-
3 files changed, 39 insertions(+), 16 deletions(-)
base-commit: 0a37921d851b94aef6900214098dc5bd62b46e26
--
2.39.1
next reply other threads:[~2023-03-08 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 12:01 Ludovic Courtès [this message]
2023-03-08 12:03 ` [bug#62047] [PATCH 1/2] packages: Use SRFI-71 instead of SRFI-11 Ludovic Courtès
2023-03-08 12:03 ` [bug#62047] [PATCH 2/2] packages: 'package-input-rewriting/spec' ignores hidden packages Ludovic Courtès
2023-03-10 11:49 ` [bug#62047] [PATCH 1/2] packages: Use SRFI-71 instead of SRFI-11 Simon Tournier
2023-03-10 16:46 ` Ludovic Courtès
2023-03-10 17:44 ` Simon Tournier
2023-03-09 20:15 ` [bug#62047] [PATCH 0/2] '--with-input' & co. no longer replace hidden packages Josselin Poiret via Guix-patches via
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=20230308120125.17560-1-ludo@gnu.org \
--to=ludo@gnu.org \
--cc=62047@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=mail@cbaines.net \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.com \
/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).