all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "(" <paren@disroot.org>, 58824@debbugs.gnu.org
Subject: [bug#58824] [PATCH 1/1] scripts: refresh: Support --list-dependent=packages.
Date: Fri, 25 Nov 2022 19:01:06 +0100	[thread overview]
Message-ID: <87ilj2ud5p.fsf@gmail.com> (raw)
In-Reply-To: <COLILZUUNFKO.34I74Z1EXIKK4@guix-framework>

Hi,
On Fri, 25 Nov 2022 at 16:25, "\( via Guix-patches" via <guix-patches@gnu.org> wrote:

> Hmm. Perhaps we could replace this with a whole new
>
>   -D, --list-dependent-packages
>
> flag?

Vagrant proposed [1] to add a flag as --machine-readable, quoting:

        I vaguely recall discussing on irc not long ago the desire for "guix
        refresh --list-dependent --machine-readable" (e.g. drop the "Building
        the following X packages would ensure 10 dependent packages are
        rebuilt:") or something similar. Would save having to pipe to cut, awk,
        sed, perl, etc. ...

Well, there is also the annoyance that hidden packages are shown so it
becomes cumbersome for piping with “guix build” for instance.  Maybe,
this patch could be tweaked to have something like,

    guix refresh --list-build-dependent PACKAGE

returning a list accepted by “guix build”.


1: <https://yhetil.org/guix/87ilj69380.fsf@contorta>

Cheers,
simon




  reply	other threads:[~2022-11-28 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 21:27 [bug#58824] [PATCH 0/1] scripts: refresh: Support --list-dependent=packages ( via Guix-patches via
2022-10-27 21:28 ` [bug#58824] [PATCH 1/1] " ( via Guix-patches via
2022-11-25  9:21   ` zimoun
2022-11-25 16:25     ` ( via Guix-patches via
2022-11-25 18:01       ` zimoun [this message]
2022-10-28 15:30 ` [bug#58824] [PATCH v2] " ( 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ilj2ud5p.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=58824@debbugs.gnu.org \
    --cc=paren@disroot.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.