all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: Add guix install command
Date: Tue, 18 Aug 2015 18:23:23 +0200	[thread overview]
Message-ID: <871tf0lg5g.fsf@gnu.org> (raw)
In-Reply-To: <87wpx7gvdw.fsf@igalia.com> (Andy Wingo's message of "Fri, 07 Aug 2015 14:01:31 +0200")

Hi!

I sympathize with the idea that ‘guix package -i’ and co. can be
cumbersome to type and maybe non-obvious, so I would be happy to add
‘guix install’, ‘guix remove’, and ‘guix search’.  I would prefer to
document ‘guix package’ as the canonical interface though, for the
reasons David and Chris gave.

However, this should be gratis in maintenance costs IMO, which means no
code duplication and equivalent functionality.

Thus, that probably means making ‘guix install’ a strict alias for ‘guix
package -i’, with the oddities that you mentioned, Andy (one could run
‘guix install foo -r bar’ and so on.)

So, what about adding a simple alias mechanism for ‘run-guix-command’ in
(guix ui) and using it to define those three aliases?  ‘guix help’ and
similar would explicitly mark them as aliases.

Eventually, we could allow users to define aliases via
~/.config/guix/aliases, say.

Thoughts?

Thanks,
Ludo’.

  parent reply	other threads:[~2015-08-18 16:23 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
2015-08-07 16:52           ` Chris Marusich
2015-08-18 16:08             ` Ludovic Courtès
2015-08-18 16:23       ` Ludovic Courtès [this message]
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=871tf0lg5g.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.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.
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.