From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Federico Beffa <beffa@ieee.org>,
ludo@gnu.org, Guix-devel <guix-devel@gnu.org>
Subject: Re: New CLI syntax for package version
Date: Sun, 10 Jan 2016 11:06:53 +1000 [thread overview]
Message-ID: <5691AEAD.4080906@uq.edu.au> (raw)
In-Reply-To: <CAKrPhPMbrV+46wpfRUwoNJR23JprUA4+eVLUKAQV=mTALfC1jg@mail.gmail.com>
On 10/01/16 08:40, Federico Beffa wrote:
> ludo@gnu.org (Ludovic Courtès) 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
>>
>> 2. underscore, <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19219#28>
>>
>> emacs_24.5:out
>>
>> 3. at, <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19219#31>
>>
>> guile@1.8
>> guile@1.8:doc
>>
>> What do people think?
> My order of preference (highest preference first) is: 3., 1., 2.
Me too.
ben
next prev parent reply other threads:[~2016-01-10 1:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 22:40 New CLI syntax for package version Federico Beffa
2016-01-10 1:06 ` Ben Woodcroft [this message]
2016-01-11 16:01 ` shakmar
2016-01-11 20:51 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2016-01-09 21:26 Ludovic Courtès
2016-01-09 22:52 ` Andreas Enge
2016-01-10 8:32 ` Ricardo Wurmus
2016-01-11 3:37 ` Christopher Allan Webber
2016-01-11 15:48 ` Eric Bavier
2016-01-12 7:50 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5691AEAD.4080906@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=beffa@ieee.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.