all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 54393@debbugs.gnu.org
Subject: [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests
Date: Tue, 15 Mar 2022 20:38:50 +0100	[thread overview]
Message-ID: <87r173huph.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ0uMiVisBH2t8qbUj-uofsto7ebhKEk_fa+q5wCFHW-Fw@mail.gmail.com> (zimoun's message of "Tue, 15 Mar 2022 11:21:07 +0100")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> Well, my point is, for example, the logic of "guix system" then "guix
> system <action> <--options>" appears to me easier to grasp and
> discover.  Idem with "guix import".  I think "guix vm" or "guix image"
> would not ease the discoverability.  What is unfortunate with "guix
> package" is that <action> and <--option> are both using dash-dash.
> Another story. :-)

I agree, ‘guix system’ and ‘guix import’ are pretty logical, consistent,
and discoverable; ‘guix package’ less so…

> I am not convinced that promoting a niche use-case would be a good
> idea.  For what my opinion is worth.  Well, I trust your experience if
> you think it is better.

There have been proposals in the past to follow a similar three-level
command scheme, such as ‘guix profile install’, etc.  While this would
be more “logical” in terms of categorization, it’s also less intuitive,
requires more typing, and overall may well be less ergonomic than
shorthands like ‘guix install’ or ‘guix edit’.

For ‘guix install’, we were guided by the rule of least surprise.  But
it’s true that in the case of ‘guix manifest’, it’s less obvious because
other package managers for instance don’t have such a command.

>> Thinking about it, another option would be to add an ‘--export-manifest’
>> option to ‘guix shell’ instead.
>
> Thinking about it, it would be the most coherent from my point of
> view.  And idem for --export-channels, no?

For ‘guix shell’ that would be strictly equivalent to ‘guix describe’.
I’m not convinced having ‘--export-channels’ would bring anything.

Thanks for your feedback!

Ludo’.




  reply	other threads:[~2022-03-15 19:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 21:50 [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests Ludovic Courtès
2022-03-14 21:51 ` [bug#54393] [PATCH 1/2] packages: Add 'package-unique-version-prefix' Ludovic Courtès
2022-03-14 21:51   ` [bug#54393] [PATCH 2/2] Add 'guix manifest' Ludovic Courtès
2022-03-15  7:18 ` [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests Liliana Marie Prikler
2022-03-15  9:27   ` Ludovic Courtès
2022-03-15  9:53     ` Liliana Marie Prikler
2022-03-15 15:17       ` Ludovic Courtès
2022-03-15  9:00 ` zimoun
2022-03-15  9:23   ` Ludovic Courtès
2022-03-15 10:21     ` zimoun
2022-03-15 19:38       ` Ludovic Courtès [this message]
2022-03-31 11:09         ` [bug#54393] [PATCH v2 1/3] packages: Add 'package-unique-version-prefix' Ludovic Courtès
2022-03-31 11:09           ` [bug#54393] [PATCH v2 2/3] environment: Export 'load-manifest' Ludovic Courtès
2022-03-31 11:09           ` [bug#54393] [PATCH v2 3/3] shell: Add '--export-manifest' Ludovic Courtès
2022-04-04 14:37             ` [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests Maxim Cournoyer
2022-04-04 21:16               ` bug#54393: " Ludovic Courtès
2022-04-05  5:48                 ` [bug#54393] " zimoun
2022-04-06  8:08                   ` Ludovic Courtès
2022-03-31 11:10         ` [bug#54393] [PATCH v2 0/3] Add '--export-manifest' to 'guix shell' Ludovic Courtès
2022-03-15 16:50 ` [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests Greg Hogan
2022-03-16  9:58   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r173huph.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=54393@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.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.