From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: New CLI syntax for package version
Date: Sun, 10 Jan 2016 09:32:06 +0100 [thread overview]
Message-ID: <878u3x4yyh.fsf@elephly.net> (raw)
In-Reply-To: <874mem8mwx.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> In <http://bugs.gnu.org/19219>, we came to the conclusion that we need a
> new syntax to denote a specific package version on the command line.
>
> The current syntax is described in the manual (info "(guix) Invoking
> guix package"). Basically, ‘guile-1.8’ refers to version 1.8.x of
> Guile; however, this syntax has proved to be ambiguous for packages
> whose name contains digits.
>
> For the new syntax, the proposals so far are:
>
> 1. slash, <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19219#25>
>
> guile:1.8/doc
> xterm-256-color:320
> emacs:24.5/out
That’s really “colon”, rather than “slash”. The slash is used to
separate the output, which reminds me of paths.
> 2. underscore, <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19219#28>
>
> emacs_24.5:out
I do not like this one.
> 3. at, <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19219#31>
>
> guile@1.8
> guile@1.8:doc
I like the “@” because it reads as “guile at [version] 1.8”. A colon to
separate the output name from the rest works just as well as a slash
(proposed above); I have no preference here.
~~ Ricardo
next prev parent reply other threads:[~2016-01-10 8:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 21:26 New CLI syntax for package version Ludovic Courtès
2016-01-09 22:52 ` Andreas Enge
2016-01-10 8:32 ` Ricardo Wurmus [this message]
2016-01-11 3:37 ` Christopher Allan Webber
2016-01-11 15:48 ` Eric Bavier
2016-01-12 7:50 ` Ricardo Wurmus
2016-01-12 9:26 ` Version numbers for VCS snapshots Ludovic Courtès
2016-01-21 4:51 ` Ben Woodcroft
2016-01-21 6:22 ` Leo Famulari
2016-01-21 9:40 ` Ricardo Wurmus
2016-01-21 18:44 ` Leo Famulari
2016-01-21 21:05 ` Ludovic Courtès
2016-02-21 4:35 ` Leo Famulari
2016-02-21 9:17 ` Alex Kost
2016-02-21 22:52 ` Leo Famulari
2016-02-22 0:09 ` Christopher Allan Webber
2016-02-23 11:53 ` Ludovic Courtès
2016-01-21 9:44 ` Ricardo Wurmus
2016-01-21 21:25 ` Ludovic Courtès
2016-01-21 22:02 ` Ricardo Wurmus
2016-01-23 22:00 ` Ludovic Courtès
2016-01-23 22:07 ` Ricardo Wurmus
2016-01-24 23:12 ` Ludovic Courtès
2016-01-21 22:08 ` Eric Bavier
2016-01-21 22:23 ` Jookia
2016-01-22 9:35 ` Andy Wingo
2016-01-22 12:31 ` Ricardo Wurmus
2016-01-23 21:51 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2016-01-09 22:40 New CLI syntax for package version Federico Beffa
2016-01-10 1:06 ` Ben Woodcroft
2016-01-11 16:01 ` shakmar
2016-01-11 20:51 ` 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=878u3x4yyh.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--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).