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: Fri, 25 Sep 2020 11:54:22 +0200	[thread overview]
Message-ID: <CAJ3okZ0AGeEuxtZR_YGLQqW2VBupsBQ5tXENbkwRZ6HmxHuZWA@mail.gmail.com> (raw)
In-Reply-To: <87wo0i2odg.fsf@gnu.org>

On Fri, 25 Sep 2020 at 11:32, Ludovic Courtès <ludo@gnu.org> wrote:
> zimoun <zimon.toutoune@gmail.com> skribis:

> > 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?
>
> I think we should really focus on individual use cases and see how to
> best address them.  For example there’s

I am not sure to understand.  The aim of pipe composition is to build
bigger use cases reusing smaller units, right? (friday's trolling
inside ;-))

My individual use case is to list all the nodes of one package.  And
by "all the nodes" I mean for all the kinds of graph types.

There is a "guix graph --path" which is really nice.  Why not "guix
graph --list-nodes"?



> <https://issues.guix.gnu.org/31442> that we could revisit now that we
> have provenance metadata and inferiors.  There’s also ‘guix size’, ‘guix
> refresh -l’, and ‘guix graph --path’.

The example above comes from this patch "guix health" that I commented
on [1]. :-)
Let's discuss that overthere.

[1] <https://issues.guix.gnu.org/31442#9>


> Perhaps we could have the backend you propose with the name ‘plain-flat’
> (or similar), but I agree with Ricardo that it seems misplaced given
> that it doesn’t show edges.

I understand.  The addition of a backend is not appropriate and
confusing (except the plain you backend you proposed).
Therefore, my proposal is to add another option to "guix graph":

  guix graph --list-nodes

similarly to "--path".  Except that "guix graph --list-nodes -t bag"
will show all the nodes of the bag graph.


WDYT?

All the best,
simon




  reply	other threads:[~2020-09-25  9:55 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
2020-09-25  9:32         ` Ludovic Courtès
2020-09-25  9:54           ` zimoun [this message]
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=CAJ3okZ0AGeEuxtZR_YGLQqW2VBupsBQ5tXENbkwRZ6HmxHuZWA@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).