unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: iyzsong@envs.net
Cc: 62577@debbugs.gnu.org, 宋文武 <iyzsong@member.fsf.org>
Subject: [bug#62577] [PATCH v2] refresh: Support select packages SUBSET by module name.
Date: Thu, 20 Apr 2023 12:18:08 +0200	[thread overview]
Message-ID: <87y1mmvov3.fsf@gnu.org> (raw)
In-Reply-To: <20230409044330.6424-1-iyzsong@envs.net> (iyzsong@envs.net's message of "Sun, 9 Apr 2023 12:43:30 +0800")

Hi,

iyzsong@envs.net skribis:

> From: 宋文武 <iyzsong@member.fsf.org>
>
> * guix/scripts/refresh.scm (%options): Support '--select module:NAME'.
> (show-help): Adjust accordingly.
> (options->update-specs): Honor the module passed by '--select'.
> * doc/guix.texi (Invoking guix refresh): Document it.

[...]

> +Select all the packages in @var{subset}, one of @code{core}, @code{non-core}
> +or @code{module:NAME}.
>  
>  The @code{core} subset refers to all the packages at the core of the
>  distribution---i.e., packages that are used to build ``everything
> @@ -14241,6 +14241,11 @@ The @code{non-core} subset refers to the remaining packages.  It is
>  typically useful in cases where an update of the core packages would be
>  inconvenient.
>  
> +The @code{module:NAME} subset refers to all the packages in a specified

s/@code{module:NAME}/@code{module:@var{name}}/

Otherwise LGTM, thanks!

Ludo’.




  reply	other threads:[~2023-04-20 10:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01  3:59 [bug#62577] [PATCH] refresh: Support select packages SUBSET by module name iyzsong--- via Guix-patches via
2023-04-08 21:27 ` Ludovic Courtès
2023-04-09  4:46   ` 宋文武 via Guix-patches via
2023-04-09  4:43 ` [bug#62577] [PATCH v2] " iyzsong--- via Guix-patches via
2023-04-20 10:18   ` Ludovic Courtès [this message]
2023-04-23  7:36     ` bug#62577: [PATCH] " 宋文武 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=87y1mmvov3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=62577@debbugs.gnu.org \
    --cc=iyzsong@envs.net \
    --cc=iyzsong@member.fsf.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).