all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ryan Prior <rprior@protonmail.com>
To: jgart <jgart@dismail.de>
Cc: Andreas Enge <andreas@enge.fr>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	guix-devel@gnu.org
Subject: Re: Transformations Shell Syntax
Date: Wed, 24 May 2023 03:06:17 +0000	[thread overview]
Message-ID: <NwO7ia53uIj5dY_wg6sbUK0Ba4S7M4GWaaPoq1SxjY0N8F3ZIaqVO-GlGw9Hq3iHFjmSJ8xH33FY4TGv1CWbVG3F0fc00jx3FMyHKd7_wBk=@protonmail.com> (raw)
In-Reply-To: <0de0483c74dca1138df849b8fd2b1193@dismail.de>

I don't like the unpredictability of jgart's original proposal, but maybe something explicit could still look similar.

Suppose you could build emacs-ement these three ways:
# no transform- this is a version packaged in Guix
guix build emacs-ement@0.5.2
# transform using `with-git-commit`
guix build emacs-ement@git-commit:8b56efa9387262514daf63151d41c9e111e79567
# transform using `with-latest`
guix build emacs-ement@latest
# transform using `with-version`
guix build emacs-ement@version:0.8.2

A short syntax for transforms would contribute to readability and ergonomic ease. Worth looking into.

Ryan


------- Original Message -------
On Tuesday, May 23rd, 2023 at 5:20 PM, jgart <jgart@dismail.de> wrote:


> 
> 
> > What disturbs me with your suggestion is that it reuses the same syntax
> 
> > that is already used for a different purpose. So in a sense you do
> > "operator overloading", and the same command line then means different
> > things depending on whether the package version is already provided by
> > Guix or not.
> 
> 
> Yes, I see how that can be an CLI smell and "not Guixonic".
> 
> Would be sweet to have something like it but I realize the negative of dirtying the current API's explicitness to get lower verbosity invocations at the shell prompt.


  reply	other threads:[~2023-05-24  3:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  6:43 Transformations Shell Syntax jgart
2023-05-23  8:16 ` Efraim Flashner
2023-05-23  9:39 ` Simon Tournier
2023-05-23 13:24 ` jgart
2023-05-23 13:55   ` Andreas Enge
2023-05-23 14:12   ` jgart
2023-05-23 14:22     ` Simon Tournier
2023-05-23 14:28     ` Andreas Enge
2023-05-23 17:20     ` jgart
2023-05-24  3:06       ` Ryan Prior [this message]
2023-05-26 15:50 ` Ludovic Courtès
2023-05-27 17:07   ` John Kehayias
2023-07-02 19:54     ` Ludovic Courtès
2023-07-05 20:23       ` John Kehayias
2023-07-03  0:01     ` jgart
2023-07-16 13:14       ` Ludovic Courtès
2023-07-23 13:00       ` Hartmut Goebel
2023-08-16 14:03         ` 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='NwO7ia53uIj5dY_wg6sbUK0Ba4S7M4GWaaPoq1SxjY0N8F3ZIaqVO-GlGw9Hq3iHFjmSJ8xH33FY4TGv1CWbVG3F0fc00jx3FMyHKd7_wBk=@protonmail.com' \
    --to=rprior@protonmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --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.