unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 35456@debbugs.gnu.org
Subject: [bug#35456] [PATCH 0/1] Add 'guix install', 'guix remove', and 'guix upgrade'
Date: Sun, 28 Apr 2019 15:26:41 +0200	[thread overview]
Message-ID: <87tvei9s6m.fsf@gnu.org> (raw)
In-Reply-To: <cadb35a8-8a63-ee72-2217-204af978ff49@web.de> (Jonathan Brielmaier's message of "Sun, 28 Apr 2019 13:26:42 +0200")

Hi Jonathan,

Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:

> On 4/27/19 6:25 PM, Ludovic Courtès wrote:
>> Thoughts?  Rejection?  Happiness?  :-)
>
> I think we shouldn't do this for the 1.0 release. We should take some
> time here. One reason is that it's quite some work to get this
> documented and then translated...

The patch provides documentation that boils down to ~10 lines since
these are just aliases.  (Also, I think it’s reasonable to say we took
our time: it had been in ‘1.0.org’ since July 2018 and we’ve been
discussing it for years before that.  :-))

> The idea of offering new commands for often used ones, is very good.
> Personally I would also like to have 'guix search' and 'guix show', as I
> use them quite often :)

Yeah, why not.

> What I like about the guix command line interface, is the consistency
> and logic. Especially if I compare it with some random (open)SUSE tool
> like zypper, which has a almost 50 subcommands ("zypper SUBCOMMAND").
> That's something we shouldn't imitate.
>
> I feel that grouping commands in subcommands and subsubcommands like
> with 'guix system' is a good idea. At the moment I see there some room
> for improvement.
>
> We have a lot of developer commands directly under 'guix', like
> download, link etc. But the most "end-user" commands are under 'guix
> package' or 'guix system'...
>
> For 'guix system' it could make sense to move 'guix system
> {container,vm-image,disk,docker-image}' to something like 'guix create'.

I agree the CLI structure could be improved in several areas.  In fact,
there have been radical proposals in the past to overhaul the whole CLI.

I think “guix install” & co. require special attention though: people
have come to expect install/remove/upgrade sub-commands from their
package manager and these are the first commands they’ll run.  It costs
us very little in terms of maintenance, but it certainly helps newcomers
get started.

Does that make sense?

Thanks for your feedback!

Ludo’.

  reply	other threads:[~2019-04-28 13:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27 16:25 [bug#35456] [PATCH 0/1] Add 'guix install', 'guix remove', and 'guix upgrade' Ludovic Courtès
2019-04-27 16:49 ` [bug#35456] [PATCH 1/1] guix package: Add 'install', 'remove', and 'upgrade' aliases Ludovic Courtès
2019-04-27 21:31   ` Ricardo Wurmus
2019-04-27 22:06     ` Tobias Geerinckx-Rice
2019-04-28 10:52     ` Ludovic Courtès
2019-04-29  8:22       ` bug#35456: " Ludovic Courtès
2019-04-28 11:26 ` [bug#35456] [PATCH 0/1] Add 'guix install', 'guix remove', and 'guix upgrade' Jonathan Brielmaier
2019-04-28 13:26   ` Ludovic Courtès [this message]
2019-04-29  7:42     ` Jonathan Brielmaier
2019-04-29 13:31       ` zimoun
2019-04-29 17:10         ` 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=87tvei9s6m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35456@debbugs.gnu.org \
    --cc=jonathan.brielmaier@web.de \
    /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).