From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35456@debbugs.gnu.org
Subject: [bug#35456] [PATCH 0/1] Add 'guix install', 'guix remove', and 'guix upgrade'
Date: Mon, 29 Apr 2019 09:42:02 +0200 [thread overview]
Message-ID: <d7475e38-5b44-0de7-bded-49b1a9f7fc07@web.de> (raw)
In-Reply-To: <87tvei9s6m.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
> 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?
If you are so confident, go ahead and make me happy by adding at least
'guix search' :)
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1813 bytes --]
next prev parent reply other threads:[~2019-04-29 7:43 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
2019-04-29 7:42 ` Jonathan Brielmaier [this message]
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=d7475e38-5b44-0de7-bded-49b1a9f7fc07@web.de \
--to=jonathan.brielmaier@web.de \
--cc=35456@debbugs.gnu.org \
--cc=ludo@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).