--- Begin Message ---
Subject: |
[PATCH 0/1] guix: graph: Add 'plain' backend. |
Date: |
Thu, 17 Sep 2020 21:39:31 +0200 |
Dear,
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:
--8<---------------cut here---------------start------------->8---
$ ./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
--8<---------------cut here---------------end--------------->8---
It is then easier to pipe with other Guix commands, for example:
--8<---------------cut here---------------start------------->8---
$ guix build $(./pre-inst-env guix graph -b plain htop | grep bash)
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
0.9 MB will be downloaded:
/gnu/store/m4qpxmn9v0jrylgbkzwssh5avzwhqil6-bash-minimal-5.0.16-doc
/gnu/store/fvhj74pghapbjvsvj27skvkra1by1965-bash-minimal-5.0.16
substituting
/gnu/store/m4qpxmn9v0jrylgbkzwssh5avzwhqil6-bash-minimal-5.0.16-doc...
downloading from
https://ci.guix.gnu.org/nar/lzip/m4qpxmn9v0jrylgbkzwssh5avzwhqil6-bash-minimal-5.0.16-doc
...
bash-minimal-5.0.16-doc 290KiB 444KiB/s 00:01 [##################] 100.0%
/gnu/store/vk4r0x7baig8jnmsqrgrqpyq8qxr4gm3-bash-5.0.16-doc
/gnu/store/v1xc4405s7xilmwhhkdj8z55wa2wlr8y-bash-5.0.16-include
/gnu/store/87kif0bpf0anwbsaw0jvg8fyciw4sz67-bash-5.0.16
/gnu/store/m4qpxmn9v0jrylgbkzwssh5avzwhqil6-bash-minimal-5.0.16-doc
/gnu/store/fvhj74pghapbjvsvj27skvkra1by1965-bash-minimal-5.0.16
--8<---------------cut here---------------end--------------->8---
Note that the manual is not updated since, since I do not know how to extend
the relevant section. Note also that "tests/guix-graph.sh" does not test any
of the backends.
All the best,
simon
zimoun (1):
guix: graph: Add 'plain' backend.
guix/graph.scm | 26 +++++++++++++++++++++++++-
1 file changed, 25 insertions(+), 1 deletion(-)
base-commit: 8d557d4167ea98dfbc200fd20f64b8da36da35a2
--
2.28.0
--- End Message ---
--- Begin Message ---
Subject: |
Re: [bug#43477] Guix aliases? |
Date: |
Mon, 05 Oct 2020 10:03:22 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Fri, 25 Sep 2020 at 17:56, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> What I meant to say was that, if we have other use cases, we can write
>> new commands or extend existing ones to cater to those needs. That’s
>> how ‘guix size’, etc. came to life. “Listing nodes” is not a use case
>> per se, but rather an means to an end; let’s focus on the ends. :-)
>>
>> (Also, let’s avoid Unix arguments; the primary composition level in Guix
>> is Scheme, not byte streams on stdout.)
>
> Well, I am not sure yet if I agree or disagree with you. :-)
> I understand the arguments and I will not have time to write a v2
> which includes your suggestion; I am interested in listing the nodes
> for some ends, not by visualizing the graph in a non-X environment.
> Therefore, feel free to close this patch submission.
OK so I’m closing for now, but let’s reopen an issue if you or someone
else thinks we really need a list-node feature or something along these
lines.
Thanks,
Ludo’.
--- End Message ---