unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "jgart" <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Transformations Shell Syntax
Date: Fri, 26 May 2023 17:50:07 +0200	[thread overview]
Message-ID: <87edn3jdn4.fsf@gnu.org> (raw)
In-Reply-To: <ab6cf744dbad90884658e812845349af@dismail.de> (jgart@dismail.de's message of "Tue, 23 May 2023 06:43:30 +0000")

Hello!

"jgart" <jgart@dismail.de> skribis:

> Uses specified commit hash:
>
> guix build emacs-ement@8b56efa9387262514daf63151d41c9e111e79567
>
> Uses specified commit hash (short):
>
> guix build emacs-ement@8b56efa
>
> Uses latest upstream release:
>
> guix build emacs-ement@latest
>
> Uses upstream version 0.8.2 if not packaged:
>
> guix build emacs-ement@0.8.2
>
> Uses the latest commit in the wip/find-room branch:
>
> guix build emacs-ement@wip/find-room

I sympathize with the will to get a more compact way to express
transformations.

Right now, command-line tools parse package specs by calling
‘specification->package+output’.  There are no restrictions on version
fields: “8b56efa9387262514daf63151d41c9e111e79567” and “latest” are
perfectly valid version fields.  Thus, if the syntax above was
implemented, we’d introduce ambiguity.

Consequently, rather than overload “@”, I believe another syntax would
need to be found.

Thanks,
Ludo’.


  parent reply	other threads:[~2023-05-26 15:50 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
2023-05-26 15:50 ` Ludovic Courtès [this message]
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=87edn3jdn4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    /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).