From 3f938d841eacb3370fcaeae41084d7594536c2d5 Mon Sep 17 00:00:00 2001 From: Florian Pelz Date: Sun, 24 Nov 2024 11:39:03 +0100 Subject: [PATCH] =?UTF-8?q?doc:=20Refer=20to=20up-to-date=20version=20of?= =?UTF-8?q?=20=E2=80=98gcc-toolchain=E2=80=99=20in=20example.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * doc/guix.texi (Writing Manifests): Write that for ‘gcc-toolchain’ we have GCC version 14 today. Change-Id: I9bfbe4a6d36b0dae16cafec86ce58ef50e64e50d --- doc/guix.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guix.texi b/doc/guix.texi index 3ca8629aef..26488b41c8 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -8797,8 +8797,8 @@ Options}). @quotation Note Manifests are @emph{symbolic}: they refer to packages of the channels @emph{currently in use} (@pxref{Channels}). In the example above, -@code{gcc-toolchain} might refer to version 11 today, but it might refer -to version 13 two years from now. +@code{gcc-toolchain} might refer to version 14 today, but it might refer +to version 16 two years from now. If you want to ``pin'' your software environment to specific package versions and variants, you need an additional piece of information: the