From: Andy Wingo <wingo@igalia.com>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: Add guix install command
Date: Fri, 07 Aug 2015 14:36:25 +0200 [thread overview]
Message-ID: <87r3nfgtrq.fsf@igalia.com> (raw)
In-Reply-To: <CAJ=RwfZ5UDr3YORQRUJj1J=yJTBVv2Bq4DbENTWXd827fr_ZGg@mail.gmail.com> (David Thompson's message of "Fri, 7 Aug 2015 08:22:20 -0400")
Thanks for the comments. Just a couple points, happy to wait for
Ludovic to get back.
On Fri 07 Aug 2015 14:22, "Thompson, David" <dthompson2@worcester.edu> writes:
>> In the case of "guix install", yes. However what would you show for
>> "guix install --help"? What would error messages show: "guix package"
>> or "guix install"? Would the user perceive it as a separate command or
>> would the fact that it is an alias be visible to the user?
>
> If we were to go the aliasing route, we could still make the --help
> and --version flags show 'guix install' with a simple pattern match on
> the arguments list.
You would have to modify the set of arguments as well. What it mean to
say e.g. "guix install --remove foo bar" ? If it were supported as an
alias and all guix package options were there, "guix package --remove
foo bar" would remove foo and bar, but you might expect "guix install
--remove foo bar" to remove foo but install bar -- but even then "guix
install --remove" is nonsensical.
To me I see the advantage of guix install as "paving the cowpaths" --
making a common use case easy while still pointing to more powerful
tools.
> every other tool encapsulates it's full functionality under a single
> subcommand: import, system, environment, gc, lint, etc.
This is a very slight advantage from the maintainer POV but from the
user's POV it's a negative thing, I think.
"guix package" just does too much: for example try "guix package
--install foo --list-available". It doesn't install foo at all, or even
try!
Andy
next prev parent reply other threads:[~2015-08-07 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 9:36 Add guix install command Andy Wingo
2015-08-06 21:08 ` Mathieu Lirzin
2015-08-07 7:47 ` Alex Kost
2015-08-07 8:45 ` Andy Wingo
2015-08-07 19:22 ` Alex Kost
2015-08-07 8:48 ` Ricardo Wurmus
2015-08-07 12:01 ` Andy Wingo
2015-08-07 12:22 ` Thompson, David
2015-08-07 12:36 ` Andy Wingo [this message]
2015-08-07 16:52 ` Chris Marusich
2015-08-18 16:08 ` Ludovic Courtès
2015-08-18 16:23 ` Ludovic Courtès
2015-08-18 17:10 ` Chris Marusich
2015-08-07 10:08 ` Mathieu Lirzin
2015-08-07 19:22 ` Alex Kost
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3nfgtrq.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=alezost@gmail.com \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.