From: Andreas Enge <andreas@enge.fr>
To: 19219@debbugs.gnu.org
Subject: bug#19219: Package names with digits following dashes
Date: Sat, 29 Nov 2014 21:31:22 +0100 [thread overview]
Message-ID: <20141129203122.GA15720@debian> (raw)
Trying to rename the font-adobe100dpi package to font-adobe-100dpi
(which is the correct name given our font conventions and even before),
I noticed the following problem:
guix build font-adobe-100dpi
looks in vain for a version 100dpi of the package named font-adobe.
The problem only occurs with digits following the dash; font-adobe-xdpi
would work.
I think we need a more sophisticated mechanism for separating package names
and versions, such as this:
- Try the compete string as a package name.
- If it does not exist, treat the part after the last dash as a version and
the part before the last dash as the name.
One could continue recursively to the second to last dash and so on, but
I think it would be easier to prohibit dashes as part of version names.
Andreas
next reply other threads:[~2014-11-29 20:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 20:31 Andreas Enge [this message]
2014-12-06 23:38 ` bug#19219: Package names with digits following dashes 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141129203122.GA15720@debian \
--to=andreas@enge.fr \
--cc=19219@debbugs.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.