From 1b108931e88374a1835fb90dd6b0ebf715f3a267 Mon Sep 17 00:00:00 2001 From: Chris Marusich Date: Wed, 10 May 2017 23:05:31 -0700 Subject: [PATCH] doc: Clarify 'guix package --search-paths' example. * doc/guix.texi (Invoking guix package): Explain why, in some cases, a user who runs the example code for 'guix package --search-paths' might see different results than what is written in the manual. --- doc/guix.texi | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/guix.texi b/doc/guix.texi index 9b2fe3fdb..57f9f7863 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -1802,7 +1802,13 @@ $ guix package -p foo -p bar --search-paths The last command above reports about the @code{GUILE_LOAD_PATH} variable, even though, taken individually, neither @file{foo} nor address@hidden would lead to that recommendation. address@hidden would lead to that address@hidden example will +only work as written if @code{guile-json} was built for the same major +version of Guile that @code{guile} refers to (e.g., 2.x.x). If that is +not the case, then this command will @emph{not} report about address@hidden because the two packages were built for different +major versions of Guile. @xref{Invoking guix package}, for more +information about how to precisely specify packages.}. @item address@hidden -- 2.12.2