guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#57460] [PATCH v3 18/18] doc: Describe how to update to a specific v


From: Hartmut Goebel
Subject: [bug#57460] [PATCH v3 18/18] doc: Describe how to update to a specific version.
Date: Tue, 20 Dec 2022 10:34:23 +0100

---
 doc/guix.texi | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/guix.texi b/doc/guix.texi
index c031c8d880..8bca0e1098 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -13932,6 +13932,25 @@ gnu/packages/multiprecision.scm:40:12: 6.1.2 is 
already the latest version of gm
 
 @end table
 
+If for some reason you don't want to update to the latest version,
+you can update to a specific version
+by appending an equal-sign and the desired version number
+to the package specification.
+However, not all updaters support this.
+
+@example
+$ guix refresh trytond-party
+gnu/packages/guile.scm:392:2: guile would be upgraded from 3.0.3 to 3.0.5
+$ guix refresh -u guile=3.0.4
+@dots{}
+gnu/packages/guile.scm:392:2: guile: updating from version 3.0.3 to version 
3.0.4...
+@dots{}
+$ guix refresh -u guile@@2.0=2.0.12
+@dots{}
+gnu/packages/guile.scm:147:2: guile: updating from version 2.0.10 to version 
2.0.12...
+@dots{}
+@end example
+
 Sometimes the upstream name differs from the package name used in Guix,
 and @command{guix refresh} needs a little help.  Most updaters honor the
 @code{upstream-name} property in package definitions, which can be used
-- 
2.30.6






reply via email to

[Prev in Thread] Current Thread [Next in Thread]