unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, 31611@debbugs.gnu.org
Subject: bug#31611: Add a property in packages to refresh to a specific version
Date: Tue, 29 May 2018 01:26:30 +0200	[thread overview]
Message-ID: <87sh6be509.fsf@fastmail.com> (raw)
In-Reply-To: <58db61ea-979f-418b-0eb6-a3bc12cfc2eb@crazy-compilers.com>

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

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

Can we simply patch the KDE importer to stick with 5.12 for now?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-05-28 23:27 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 [this message]
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

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=87sh6be509.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=31611@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).