unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, 43477@debbugs.gnu.org
Subject: [bug#43477] [PATCH 0/1] guix: graph: Add 'plain' backend.
Date: Thu, 24 Sep 2020 17:47:18 +0200	[thread overview]
Message-ID: <CAJ3okZ34BA9Q+9+b0T7vAJwN6ZgoVx_ceukn+iiV5eAvWpqLoQ@mail.gmail.com> (raw)
In-Reply-To: <87o8lv8cao.fsf@gnu.org>

Hi,

On Thu, 24 Sep 2020 at 16:44, Ludovic Courtès <ludo@gnu.org> wrote:

> >> Is that still a graph, though…?
> >
> > I agree it is not a graph.  Instead of 'plain' the name could be
> > 'list-nodes', or whatever.

The point is I am often doing

   guix graph -t <type> <pkg> | grep label | grep <stuff>

then I select what I am interested in and reuse it with another Guix
command (size or graph again or show or whatever).  And the regexp
directly pick the package name is too complicated to remember, so yes
I could have a script.

For example, I would to know if all the packages in my profile are OK
about CVE and already archived on SWH, with the proposed patch, it is
simply:

   guix package -I | cut -f1 \
     | xargs -I{} ./pre-inst-env guix graph -b list-nodes {} \
     | xargs -I{} guix lint -c cve,archival {}

and obviously instead "-t bag" could be used.

Well, another option as "--list-nodes" could be added.  WDTY?


> What would be super useful is a tree representation, like so:
>
>   guile
>   + pkg-config
>   + libgc
>   |- pkg-config […]
>   + gmp
>   |- m4
>   + libffi
>   + bash-minimal
>
> (With the right Unicode characters, of course.  :-))

It could be nice.  And yeah, it will be the correct backend name: plain. :-)


All the best,
simon




  reply	other threads:[~2020-09-24 16:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 19:39 [bug#43477] [PATCH 0/1] guix: graph: Add 'plain' backend zimoun
2020-09-17 19:40 ` [bug#43477] [PATCH 1/1] " zimoun
2020-09-18  9:35 ` [bug#43477] [PATCH 0/1] " Mathieu Othacehe
2020-09-18 19:59   ` zimoun
2020-09-18 12:34 ` Ricardo Wurmus
2020-09-18 20:04   ` zimoun
2020-09-24 14:44     ` Ludovic Courtès
2020-09-24 15:47       ` zimoun [this message]
2020-09-25  9:32         ` Ludovic Courtès
2020-09-25  9:54           ` zimoun
2020-09-25 10:11             ` Ricardo Wurmus
2020-09-25 12:22               ` [bug#43477] Guix aliases? (was: [bug#43477] [PATCH 0/1] guix: graph: Add 'plain' backend.) zimoun
2020-09-25 15:56                 ` [bug#43477] Guix aliases? Ludovic Courtès
2020-09-25 17:00                   ` zimoun
2020-10-05  8:03                     ` bug#43477: " 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=CAJ3okZ34BA9Q+9+b0T7vAJwN6ZgoVx_ceukn+iiV5eAvWpqLoQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=43477@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    /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).