From: Mathieu Othacehe <othacehe@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 43477@debbugs.gnu.org
Subject: [bug#43477] [PATCH 0/1] guix: graph: Add 'plain' backend.
Date: Fri, 18 Sep 2020 11:35:55 +0200 [thread overview]
Message-ID: <877dsr1l6s.fsf@gnu.org> (raw)
In-Reply-To: <20200917193931.14699-1-zimon.toutoune@gmail.com> (zimoun's message of "Thu, 17 Sep 2020 21:39:31 +0200")
Hello zimoun,
> I am always annoyed when I use "guix graph" because most of the time I run:
>
> guix graph htop | grep label
>
> or something along these lines. Instead, the patch avoids the grep part:
What's your exact use case? Note that you can run something like:
--8<---------------cut here---------------start------------->8---
guix gc -R `guix build htop`
--8<---------------cut here---------------end--------------->8---
to print the transitive closure of htop.
> $ ./pre-inst-env guix graph -b plain htop
> htop@3.0.2
> autoconf@2.69
> perl@5.30.2
> m4@1.4.18
> automake@1.16.2
> autoconf-wrapper@2.69
> guile@2.0.14
> pkg-config@0.29.2
> libffi@3.3
> bash-minimal@5.0.16
> libunistring@0.9.10
> libltdl@2.4.6
> libgc@8.0.4
> gmp@6.2.0
> bash@5.0.16
> readline@8.0.4
> ncurses@6.2
The issue with this approach is that the output is not really a graph,
just a list of nodes.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-09-18 9:37 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 ` Mathieu Othacehe [this message]
2020-09-18 19:59 ` [bug#43477] [PATCH 0/1] " 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
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=877dsr1l6s.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=43477@debbugs.gnu.org \
--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).