From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: perl-getopt-long version string contains a letter
Date: Wed, 06 Mar 2019 16:56:29 +0100 [thread overview]
Message-ID: <87k1hcf13m.fsf@gnu.org> (raw)
In-Reply-To: <20190304183140.GA5771@macbook41> (Efraim Flashner's message of "Mon, 4 Mar 2019 20:31:40 +0200")
Hello,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Mon, Mar 04, 2019 at 05:54:38PM +0100, Ricardo Wurmus wrote:
>> Hi Guix,
>>
>> perl-getopt-long has a version string "v2.49.1". If we change this to
>> "2.49.1", will installed packages not be upgraded? What can be done in
>> this case?
>>
>
> As I've wrapped my head around it, Guix doesn't believe in "upgrades"
> and "downgrades", just in changes in dependencies. So if the version
> string loses the leading "v" I suppose ASCIIbetically v2.49.1 is a
> higher value than 2.49.1,
Indeed:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (version>? "v2.49.1" "2.49.1")
$21 = #t
--8<---------------cut here---------------end--------------->8---
Perhaps what could be done is to deprecate the package with “v2.49.1”,
like so:
(define-public x
(package
;; …
(version "2.49.1")))
(define w/wrong-version
(package
(inherit x)
(version "v2.49.1") ;wrong version string
(properties `((superseded . ,x)))))
That should cause upgrades from the wrong version to the new one, even
if the new one is not ‘version>?’.
Thoughts?
Ludo’.
prev parent reply other threads:[~2019-03-06 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 16:54 perl-getopt-long version string contains a letter Ricardo Wurmus
2019-03-04 18:31 ` Efraim Flashner
2019-03-06 15:56 ` Ludovic Courtès [this message]
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=87k1hcf13m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@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.