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 15:55:28 +0200 [thread overview]
Message-ID: <ZGzF0Es100o4lCVp@jurong> (raw)
In-Reply-To: <95989e12b8be444d908a4401c1fb55d2@dismail.de>
Hello,
Am Tue, May 23, 2023 at 01:24:00PM +0000 schrieb jgart:
> I was openly ideating on having shell syntax like we do currently for emacs-ement@0.9.3, for example, but for a subset of package transformation options as well.
I am a bit wary of too much intelligence in interpreting commands, at the
expense of clarity (also for the user - what do they really do?)
Right now, "guix build emacs-ement@0.9.3" means "build the package
emacs-ement at version 0.9.3, which is available somewhere in my
channels".
I think your semantics ends up meaning "try to make sense of the version
field, and give me the package at this version". This is actually quite
different - for instance, it means the package is not vetted by Guix
developers. So there may even be security implications.
In my opinion we should strive for simplicity in commands, it should
always be clear what a specific command line does and not depend on
context, and the guix tool should not second guess what we want to do
when invoking a given command.
Andreas
next prev parent reply other threads:[~2023-05-23 14:04 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 [this message]
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
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=ZGzF0Es100o4lCVp@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).