GNU bug report logs - #60079
[PATCH] guix: gexp: Clarify what output can be in gexp module commentary.

Previous Next

Full log

Message #8 received at 60079 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: jgart <jgart <at> dismail.de>
Cc: 60079 <at> debbugs.gnu.org
Subject: Re: bug#60079: [PATCH] guix: gexp: Clarify what output can be in
 gexp module commentary.
Date: Wed, 21 Dec 2022 14:31:45 +0100

Hi jgart,

jgart <jgart <at> dismail.de> skribis:

> --- a/guix/gexp.scm
> +++ b/guix/gexp.scm
> @@ -139,10 +139,11 @@ (define-module (guix gexp)
>  ;;; This module implements "G-expressions", or "gexps".  Gexps are like
>  ;;; S-expressions (sexps), with two differences:
>  ;;;
> -;;;   1. References (un-quotations) to derivations or packages in a gexp are
> -;;;      replaced by the corresponding output file name; in addition, the
> -;;;      'ungexp-native' unquote-like form allows code to explicitly refer to
> -;;;      the native code of a given package, in case of cross-compilation;
> +;;;   1. References (un-quotations) to derivations or packages in a gexp
> +;;;   are replaced by the corresponding output store path or file name;
> +;;;   in addition, the 'ungexp-native' unquote-like form allows code to
> +;;;   explicitly refer to the native code of a given package, in case
> +;;;   of cross-compilation;

I prefer not to apply this patch: it worsens indentation and adds the
words “store path”, which AFAICS bring nothing.

Thanks anyway for taking a look,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.