[bug#57460,v3,18/18] doc: Describe how to update to a specific version.
Commit Message
---
doc/guix.texi | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
Comments
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> ---
> doc/guix.texi | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
Please add a commit log.
> +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.
s/equal-sign/equal sign/
(You might want to “fill” the paragraph too, to avoid those spurious
line breaks.)
Maybe replace the last sentence with something more practical like:
Note that not all updaters support this; an error is reported when an
updater cannot refresh to the specified version.
Ludo’.
@@ -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