From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: 19219@debbugs.gnu.org, request@debbugs.gnu.org
Subject: bug#19219: Package names with digits following dashes
Date: Thu, 10 Dec 2015 14:36:26 +0100 [thread overview]
Message-ID: <87si3ah1d1.fsf@gnu.org> (raw)
In-Reply-To: <874mfssrxd.fsf@gnu.org> (Mathieu Lirzin's message of "Tue, 08 Dec 2015 19:42:38 +0100")
Mathieu Lirzin <mthl@gnu.org> skribis:
> I had the same issue when trying to create a package named
> 'rxvt-unicode-256-color'. I have tried to fix
> ‘package-name->name+version’ by matching the last hyphen and check if
> the next character is a number.
Sounds like a reasonable approach (better than what I submitted), but we
would need test for the various corner cases. Could you augment the
test that’s in tests/utils.scm?
> The result was a fail attempt to rebuild the earth:
This is because everything depends on (guix build utils).
But we’re right in time to make this change in ‘core-updates’.
Thanks!
Ludo’.
next prev parent reply other threads:[~2015-12-10 13:37 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 [this message]
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
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=87si3ah1d1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19219@debbugs.gnu.org \
--cc=mthl@gnu.org \
--cc=request@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 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).