unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 19219@debbugs.gnu.org, Mathieu Lirzin <mthl@gnu.org>
Subject: bug#19219: New command-line syntax for package + version?
Date: Fri, 1 Jan 2016 16:45:18 -0500	[thread overview]
Message-ID: <20160101214518.GA12106@jasmine> (raw)
In-Reply-To: <20160101212540.GC11284@jasmine>

On Fri, Jan 01, 2016 at 04:25:40PM -0500, Leo Famulari wrote:
> On Fri, Jan 01, 2016 at 04:55:40PM +0100, Ludovic Courtès wrote:
> > Efraim Flashner <efraim@flashner.co.il> skribis:
> > 
> > > On Wed, 30 Dec 2015 20:16:31 -0500
> > > Leo Famulari <leo@famulari.name> wrote:
> > >
> > >> On Wed, Dec 30, 2015 at 11:45:14PM +0100, Mathieu Lirzin wrote:
> > >>  [...]  
> > >>  [...]  
> > >>  [...]  
> > >>  [...]  
> > >>  [...]  
> > >>  [...]  
> > >> > 
> > >> > I'm OK with that.  Since choosing the reserved characters is not a
> > >> > technical decision, maybe we could poll users?  
> > >> 
> > >> I think we should poll a big list of packages and see which characters
> > >> are most safe to use.
> > >> 
> > >> The question is: which big list? Debian's?
> > >> 
> > >> 
> > >  
> > > When debian adopted multiarch 
> > 
> > [...]
> > 
> > I forgot to reply to Leo’s message, but it seems clear to me that it
> > only makes sense to discuss on Guix mailing lists.  I don’t think anyone
> > else cares about the syntax of Guix’s command-line interface.  ;-)
> 
> I don't mean that we should discuss it on Debian's mailing list. I mean
> that we should consult the largest list of packages that we can find in
> order to learn which characters are safest to choose as reserved. Debian
> has a very long list of packages.

Of course, Debian has to choose how to name their packages, so the list
provided by `apt-cache pkgnames` is not the same as the list of upstream
names. But it does give some idea of what is possible once everything is
packaged.

I did this:
$ apt-cache pkgnames | tr -d 'a-zA-Z0-9' | tr -d - | tr -d '\n'

The only remaining characters were '.' and '+'. So it could be possible
to reserve : and @ without causing too many problems.

> 
> > 
> > Ludo’.

  reply	other threads:[~2016-01-02  0:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 20:31 bug#19219: Package names with digits following dashes Andreas Enge
2014-12-06 23:38 ` Ludovic Courtès
2015-12-08 18:42   ` Mathieu Lirzin
2015-12-10 13:36     ` Ludovic Courtès
2015-12-21 18:27       ` Mathieu Lirzin
2015-12-21 21:46         ` Ludovic Courtès
2015-12-22 21:23           ` Mathieu Lirzin
2015-12-23  8:05             ` Alex Kost
2015-12-30 14:07             ` bug#19219: New command-line syntax for package + version? Ludovic Courtès
2015-12-30 22:45               ` Mathieu Lirzin
2015-12-31  1:16                 ` Leo Famulari
2015-12-31  8:09                   ` Efraim Flashner
2016-01-01 15:55                     ` Ludovic Courtès
2016-01-01 21:25                       ` Leo Famulari
2016-01-01 21:45                         ` Leo Famulari [this message]
2016-01-02  3:18                           ` carl hansen
2015-12-31  8:19                 ` Alex Kost
2015-12-31 11:27                 ` Ludovic Courtès
2015-12-31 16:26                   ` Christopher Allan Webber
2016-01-01 20:36                     ` Andreas Enge
2016-01-09  3:04                   ` Mathieu Lirzin
2016-01-18  8:10                     ` Ludovic Courtès
2016-01-18  8:31                       ` Mathieu Lirzin
2016-03-02 21:10                         ` Mathieu Lirzin

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=20160101214518.GA12106@jasmine \
    --to=leo@famulari.name \
    --cc=19219@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mthl@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).