unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: jgart <jgart@dismail.de>
Cc: Simon Tournier <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: Transformations Shell Syntax
Date: Tue, 23 May 2023 16:28:50 +0200	[thread overview]
Message-ID: <ZGzNovpChBRb1jTn@jurong> (raw)
In-Reply-To: <412fbcf010594abbac4c653536022455@dismail.de>

Am Tue, May 23, 2023 at 02:12:02PM +0000 schrieb jgart:
> > I think your semantics ends up meaning "try to make sense of the version
> > field, and give me the package at this version". 
> Aren't these the current semantics of guix package transformations though? I'm just proposing shell syntax for them.

Yes, indeed. So there already is shell syntax, it is just a bit unweildy
and verbose.

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.

Like Simon writes, let us be explicit.

Andreas



  parent reply	other threads:[~2023-05-23 14:29 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 [this message]
2023-05-23 17:20     ` jgart
2023-05-24  3:06       ` Ryan Prior
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

  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=ZGzNovpChBRb1jTn@jurong \
    --to=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 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).