unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 28446@debbugs.gnu.org
Subject: bug#28446: linux-libre@4.1 should select 4.1.x, not 4.13.x
Date: Tue, 26 Sep 2017 00:26:15 -0400	[thread overview]
Message-ID: <87vak6gk60.fsf@netris.org> (raw)
In-Reply-To: <87ingc2p51.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 21 Sep 2017 14:48:58 +0200")

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

>> Currently, the package specification "linux-libre@4.1" selects version
>> 4.13.  It should instead select version 4.1.
>
> We consider everthing following the “@” a version string prefix.  Since
> versions are arbitrary strings “4.1” is considered a valid prefix of
> “4.13”.  If a user supplied the version string “4.1.” they would get the
> appropriate package.
>
> The current implementation sorts all matches in decreasing version order
> and picks the package with the highest version.  This is implemented in
> (gnu packages) with “%find-packages”, “find-best-packages-by-name”, and
> “find-packages-by-name”.
>
> Should we try to make the code understand version strings better and
> compare substrings of the version string?  We could fall back to using
> “string-prefix?” when the substring is not a number.

One possible approach would be as follows: if the last character of the
specification is a digit, then priority should be given to versions that
have a non-digit (or end-of-string) after the last matching character.

Put another way, if the provided specification {SPEC} ends with a digit,
then we should first search based on the following regexp:

  ^{SPEC}[^0-9]

if no matches are found, then fall back to:

  ^{SPEC}

This would gracefully handle the common case where groups of adjacent
digits should be considered as single numbers, while still allowing
prefixes of other numeric components such as dates or commit ids.

I admit that this proposal lacks elegance.  So far I have no better
ideas.

      Mark

  parent reply	other threads:[~2017-09-26  4:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 15:07 bug#28446: linux-libre@4.1 should select 4.1.x, not 4.13.x Mark H Weaver
2017-09-21 12:48 ` Ricardo Wurmus
2017-09-22  1:53   ` Chris Marusich
2017-09-22  8:04     ` Ricardo Wurmus
2017-09-26  4:26   ` Mark H Weaver [this message]
2018-05-13 11:31     ` 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=87vak6gk60.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=28446@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).