unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#31611: Add a property in packages to refresh to a specific version
@ 2018-05-27 17:55 Hartmut Goebel
  2018-05-28 23:26 ` Marius Bakke
  2023-08-11 19:59 ` Maxim Cournoyer
  0 siblings, 2 replies; 6+ messages in thread
From: Hartmut Goebel @ 2018-05-27 17:55 UTC (permalink / raw)
  To: 31611

`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

-- 
Regards
Hartmut Goebel

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#31611: Add a property in packages to refresh to a specific version
  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
  2023-08-11 19:59 ` Maxim Cournoyer
  1 sibling, 1 reply; 6+ messages in thread
From: Marius Bakke @ 2018-05-28 23:26 UTC (permalink / raw)
  To: Hartmut Goebel, 31611

[-- 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 --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#31611: Add a property in packages to refresh to a specific version
  2018-05-28 23:26 ` Marius Bakke
@ 2018-05-29 16:55   ` Hartmut Goebel
  2018-06-19 14:17     ` Marius Bakke
  0 siblings, 1 reply; 6+ messages in thread
From: Hartmut Goebel @ 2018-05-29 16:55 UTC (permalink / raw)
  To: Marius Bakke, 31611

Am 29.05.2018 um 01:26 schrieb Marius Bakke:
> Can we simply patch the KDE importer to stick with 5.12 for now?

Not a good solution IMHO. For now I can also use "guix download"as a
work-around This is not comfortable, but avoids having a forgotten
"feature" in the code.

-- 
Regards
Hartmut Goebel

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#31611: Add a property in packages to refresh to a specific version
  2018-05-29 16:55   ` Hartmut Goebel
@ 2018-06-19 14:17     ` Marius Bakke
  2018-06-20  7:38       ` Hartmut Goebel
  0 siblings, 1 reply; 6+ messages in thread
From: Marius Bakke @ 2018-06-19 14:17 UTC (permalink / raw)
  To: Hartmut Goebel, 31611

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

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> Am 29.05.2018 um 01:26 schrieb Marius Bakke:
>> Can we simply patch the KDE importer to stick with 5.12 for now?
>
> Not a good solution IMHO. For now I can also use "guix download"as a
> work-around This is not comfortable, but avoids having a forgotten
> "feature" in the code.

I'm not convinced that adding a property to some 80 packages is better
than patching the importer.  To me this problem seems very
importer-specific (knowing what releases are considered LTS).

As a middle ground, perhaps we could add a "--select" argument to guix
import, e.g: "--select=REGEX    Only consider versions matching REGEX".

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#31611: Add a property in packages to refresh to a specific version
  2018-06-19 14:17     ` Marius Bakke
@ 2018-06-20  7:38       ` Hartmut Goebel
  0 siblings, 0 replies; 6+ messages in thread
From: Hartmut Goebel @ 2018-06-20  7:38 UTC (permalink / raw)
  To: Marius Bakke, 31611


[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]

Am 19.06.2018 um 16:17 schrieb Marius Bakke:
> I'm not convinced that adding a property to some 80 packages is better
> than patching the importer.  To me this problem seems very
> importer-specific (knowing what releases are considered LTS).

I disagree this is imported specific. Imagine we would like to provide
different still supported versions of e.g. Python (3,.4, 3.5, 3.6, 3.7)
or openssl (1.0 and 1.1).


> As a middle ground, perhaps we could add a "--select" argument to guix
> import, e.g: "--select=REGEX    Only consider versions matching REGEX".

This would improve the current situation :-)

-- 

Regards
Hartmut Goebel

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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#31611: Add a property in packages to refresh to a specific version
  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
@ 2023-08-11 19:59 ` Maxim Cournoyer
  1 sibling, 0 replies; 6+ messages in thread
From: Maxim Cournoyer @ 2023-08-11 19:59 UTC (permalink / raw)
  To: Hartmut Goebel; +Cc: 31611-done

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




^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-08-11 20:01 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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

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).