|
From: | Ben Woodcroft |
Subject: | Re: [PATCHES] Add ruby-mini-portile-2, upgrade ruby-nokogiri |
Date: | Thu, 31 Dec 2015 10:44:36 +1000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
On 24/12/15 05:04, Leo Famulari wrote:
On Tue, Dec 22, 2015 at 10:29:49PM +1000, Ben Woodcroft wrote:Nokogiri now requires an updated version of mini_portile (the gem was renamed to mini_portile2), but given that new versions of the 0.6.x branch still seem to be released I think keeping a separate mini_portile package is the go.These are the results of `guix refresh -l ruby-mini-portile`: Building the following 4 packages would ensure 6 dependent packages are rebuilt: ruby-pygmentize-0.0.3 ruby-nokogiri-diff-0.2.0 ruby-sanitize-4.0.0 bio-blastxmlparser-2.0.4 Looks like a bit of work to properly upgrade all these and their referrers to ruby-mini-portile-2! But it may be worth it to watch them in the future and try to drop ruby-mini-portile when it becomes possible, assuming upstream plans to deprecate it eventually.
and I just packaged another one..
I came across a subtle problem. Because the old miniportile is "ruby-mini-portile" and the new one is "ruby-mini-portile-2" but they share the same package name field, there doesn't seem to be any way to install the old miniportile from the command line:LGTM, thanks! Pushed as 1b9d4e2e20.
$ ./pre-inst-env guix package -i ruby-mini-portile The following package will be upgraded:ruby-mini-portile 0.6.2 → 2.0.0 /gnu/store/0wlnhs4ymzj1mcm6wvc2y1ngvpj7wwls-ruby-mini-portile-2.0.0
I think maybe we should rename the old version to ruby-mini-portile-0, but keep the name of ruby-mini-portile-2. This would entail modifying the dependent packages but this is doable I would think.
WDYT? Thanks, ben
[Prev in Thread] | Current Thread | [Next in Thread] |