From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 31611-done@debbugs.gnu.org
Subject: bug#31611: Add a property in packages to refresh to a specific version
Date: Fri, 11 Aug 2023 15:59:48 -0400 [thread overview]
Message-ID: <87ttt5l58r.fsf@gmail.com> (raw)
In-Reply-To: <58db61ea-979f-418b-0eb6-a3bc12cfc2eb@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 27 May 2018 19:55:09 +0200")
Hi Hartmut,
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> `guix refresh` always fetches the newest version of packages. This might
> not be desired in all cases. E.g. one might want to keep some still
> supported "major" upstream-version and not yet update to the next
> "major" version.
>
> Ludo suggested to add a property in packages that would instruct
> updaters to restrict the version search space to a given regexp.
>
> Rational: Example: KDE Plasma 5 has 5.12 as long-term-support (LTS)
> version, while 5.14 has already being released. Do easy maintenance of
> dependent packages, sticking to 5.12.x micht be desired.
>
> Original discussion:
> https://lists.gnu.org/archive/html/guix-devel/2018-02/msg00055.html
It's now possible to refresh to a specific version with the '=' syntax,
as documented in 'info "(guix)Invoking guix refresh"':
E.g.:
--8<---------------cut here---------------start------------->8---
guix refresh qtbase@5=5.15.10 -> qtbase would be upgraded from 5.15.8 to 5.15.10
--8<---------------cut here---------------end--------------->8---
Closing!
--
Thanks,
Maxim
prev parent reply other threads:[~2023-08-11 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 17:55 bug#31611: Add a property in packages to refresh to a specific version Hartmut Goebel
2018-05-28 23:26 ` Marius Bakke
2018-05-29 16:55 ` Hartmut Goebel
2018-06-19 14:17 ` Marius Bakke
2018-06-20 7:38 ` Hartmut Goebel
2023-08-11 19:59 ` Maxim Cournoyer [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
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=87ttt5l58r.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=31611-done@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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).