From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 34651@debbugs.gnu.org
Subject: bug#34651: guix commands should print a message, if they produce only trivial output by default
Date: Mon, 25 Feb 2019 17:24:56 +0100 [thread overview]
Message-ID: <20190225172456.242b2df0@alma-ubu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
I noticed that if you call "guix COMMAND" for some COMMANDs without any
options given, they produce something which is not very useful to the
user. I first noticed it with guix pack:
When "guix pack" is run without any options, it builds an empty pack:
$ guix pack
/gnu/store/2ys9fn6h95209piqhyxli5pf2c4mp7zp-tarball-pack.tar.gz
$ tar tzvf /gnu/store/2ys9fn6h95209piqhyxli5pf2c4mp7zp-tarball-pack.tar.gz
drwxrwxr-t root/root 0 1970-01-01 01:00 ./gnu/store/
dr-xr-xr-x root/root 0 1970-01-01 01:00 ./gnu/store/w659mjmzwyhv62sd35y2pv5nrg5xkl7j-profile/
dr-xr-xr-x root/root 0 1970-01-01 01:00 ./gnu/store/w659mjmzwyhv62sd35y2pv5nrg5xkl7j-profile/etc/
-r--r--r-- root/root 414 1970-01-01 01:00 ./gnu/store/w659mjmzwyhv62sd35y2pv5nrg5xkl7j-profile/etc/profile
-r--r--r-- root/root 37 1970-01-01 01:00 ./gnu/store/w659mjmzwyhv62sd35y2pv5nrg5xkl7j-profile/manifest
I think from a user perspective it would be better to print a help
message and not build an empty pack.
On the other hand, I tried out other guix commands and at least it is a
consistent behaviour, they start with the default values, like "guix
graph" outputs just an empty graph.
"guix system" complains it needs a subcommand, which is a different
case.
But then again we have this complaint:
guix system container
guix system: error: wrong number of arguments for action 'container'
WDYT?
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2019-02-25 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 16:24 Björn Höfling [this message]
2019-03-01 17:29 ` bug#34651: guix commands should print a message, if they produce only trivial output by default swedebugia
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=20190225172456.242b2df0@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=34651@debbugs.gnu.org \
/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).