From: me--- via <help-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Output all dependencies recursively for package
Date: Mon, 01 Feb 2021 17:21:09 +0100 [thread overview]
Message-ID: <87tuqvhi8a.fsf@nckx> (raw)
In-Reply-To: <CAJ3okZ1jbVCdejPLPmQPXpkCSDNHCvnOBOs2fg=rD6gOsBjjqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
zimoun 写道：
> There would be the same philosophical discussion about what
> constitutes a "refresh". ;-)
>
> Joke aside, this "hello@2.10 depends on the following 20
> packages:" is
> annoying because you have to pipe " | cut -d':' -f2" to get what
> you
> are really interested in.
Oh, I agree with you on both points, Simon!
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-02-01 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 12:59 Output all dependencies recursively for package Phil
2021-01-31 15:03 ` Joshua Branson
2021-02-01 1:32 ` Tobias Geerinckx-Rice
2021-02-01 6:26 ` zimoun
2021-02-01 16:21 ` me--- via [this message]
2021-02-01 19:36 ` Phil
2021-01-31 15:30 ` Efraim Flashner
2021-01-31 19:09 ` zimoun
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=87tuqvhi8a.fsf@nckx \
--to=help-guix@gnu.org \
--cc=me@tobias.gr \
--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.
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).