unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix refresh to a specific version?
Date: Sun, 19 Jun 2022 11:23:13 +0200	[thread overview]
Message-ID: <257ef3b8-cbfb-20d6-2f2a-9ffa472606c2@crazy-compilers.com> (raw)
In-Reply-To: <8735g3fght.fsf@gnu.org>

Hi,

Am 17.06.22 um 17:37 schrieb Ludovic Courtès:
> It’s currently not possible, but pretty much all the machinery is there,
> in importers.  It’s a low-hanging fruit that I think we should pick!

I gave it a try and discovered that we need to discuss the interface and 
design:

One can already specify a version, which defines the package to be 
updated. The respective place the code has the comment

Take either the specified version or the latest one.

and this was added by you (Ludo) in 
4b9b3cbbc45afa3e374889847d4ab8673b8b2db2 (April 2015):

refresh: Allow users to refer to specific package versions.

* guix/scripts/refresh.scm (guix-refresh): Use 'specification->package'
   instead of 'find-packages-by-name'.  This allows users to specify
   things like "qt-4.8.6".


Beside this, I'm unconfident about the implementation: Currently refresh 
passes around package objects and passes this to the updater. When 
updating to a specific version, we need to pass around both the package 
and the desired version, which implies case-handling at many places. Any 
idea how to solve this elegantly?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



  reply	other threads:[~2022-06-19  9:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 11:34 guix refresh to a specific version? Hartmut Goebel
2022-06-17 15:37 ` Ludovic Courtès
2022-06-19  9:23   ` Hartmut Goebel [this message]
2022-06-22 13:35     ` Ludovic Courtès
2022-06-28  8:08       ` Hartmut Goebel
2022-06-30 11:58         ` Ludovic Courtès
2022-07-04 14:06           ` Hartmut Goebel
2022-07-04 15:53             ` zimoun
2022-07-05  9:32               ` bokr
2022-07-05  9:40                 ` Tobias Geerinckx-Rice
2022-07-05 10:17                 ` zimoun
2022-07-07  7:45             ` Ludovic Courtès
2022-08-28 13:20               ` Hartmut Goebel
2022-06-28 10:59 ` Maxime Devos

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=257ef3b8-cbfb-20d6-2f2a-9ffa472606c2@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).