unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias <john.kehayias@protonmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: jgart@dismail.de, guix-devel@gnu.org
Subject: Re: Transformations Shell Syntax
Date: Wed, 05 Jul 2023 20:23:30 +0000	[thread overview]
Message-ID: <87edlmkszl.fsf@protonmail.com> (raw)
In-Reply-To: <878rbyum14.fsf@gnu.org>

Hello,

On Sun, Jul 02, 2023 at 09:54 PM, Ludovic Courtès wrote:

> HI,
>
> John Kehayias <john.kehayias@protonmail.com> skribis:
>
>> As one who also would like a shorter syntax option, here's a quick
>> thought: what about a short version of what we have for when there
>> is only one package given or it can be applied to all packages/be a
>> positional argument? An example is perhaps best, so what if we could
>> write:
>>
>> guix shell <package> --with-latest
>>
>> or guix shell <package> -<a letter which is available>
>>
>> which is short for
>>
>> guix shell <package> --with-latest=<package>
>>
>> or even
>>
>> guix shell <package1> <package2> <package3> --with-latest
>>
>> to apply to all packages.
>
> This should be possible.  We should check the option parsers and
> transformation procedures in (guix transformations).
>

Sounds good, seems like a nice little project for someone. I'll pass
for the time being as I catch up on my patches and trying to review
more. (And I want to add some basic multi-arch support to the FHS
container, too.)

>> Or something like
>>
>> guix shell <package1> <package2> --with-git-url=<a git url for package3> <package3>
>>
>> and so on.
>
> This I’m unsure; one might argue that it’s also ambiguous, I’d always
> wonder what ‘--with-git-url’ applies to.
>

I generally agree; I'm not a fan of too much positional-ness in
arguments as it can get confusing. Though we do have --development for
guix shell already, of course.



  reply	other threads:[~2023-07-05 20:24 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
2023-05-27 17:07   ` John Kehayias
2023-07-02 19:54     ` Ludovic Courtès
2023-07-05 20:23       ` John Kehayias [this message]
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=87edlmkszl.fsf@protonmail.com \
    --to=john.kehayias@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --cc=ludo@gnu.org \
    /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).