GNU bug report logs - #53657
inconsistent parsing of the channel sexp's

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53657 in the body.
You can then email your comments to 53657 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: Attila Lendvai <attila <at> lendvai.name>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: inconsistent parsing of the channel sexp's
Date: Mon, 31 Jan 2022 12:30:18 +0000

pull.scm does this with channel files, e.g. with /etc/guix/channels.scm:

(load* file (make-user-module '((guix channels))))

i.e. this way field values are EVAL'd. beside the big can of worms that this opens up, it also means that e.g. the name field must be quoted: (name 'guix).

then at other occurrences of channels, an sexp parser is used to read them, e.g. in the 'dependencies field of a .guix-channel entry. see READ-CHANNEL-METADATA in guix/channels.scm.

here the name field is not EVAL'd, and thus it must be specified without quotes: (name guix).

this leads to an actual issue that channel dependencies don't match up, unless the name is without quotes in the dependencies list specification.

--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Awareness isn’t something we own; awareness isn’t something we possess. Awareness is actually what we are.”
	— Adyashanti (1962–)

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

From: Ricardo Wurmus <rekado <at> elephly.net>
To: 53657 <at> debbugs.gnu.org
Subject: inconsistent parsing of the channel sexp's
Date: Tue, 01 Feb 2022 15:41:27 +0100

Thanks for the bug report.

I feel like I’m missing something here.

> this leads to an actual issue that channel dependencies don't match up,
> unless the name is without quotes in the dependencies list
> specification.

I don’t understand what it means for “channel dependencies” to “match
up”.  How is this an issue?

I’ll say that I agree that there’s an apparent inconsistency (as
evidenced also by commit 52e64b21be50e2c5febd7bf1accd88ffdc05a4bb, which
corrected a mistake in the documentation that used an explicit quote), I
just don’t see yet how it leads to a practical problem.

Could you please elaborate?

-- 
Ricardo

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Attila Lendvai <attila <at> lendvai.name>
Cc: 53657 <at> debbugs.gnu.org
Subject: Re: bug#53657: inconsistent parsing of the channel sexp's
Date: Wed, 02 Mar 2022 11:44:56 +0100

Hi,

Attila Lendvai <attila <at> lendvai.name> skribis:

> pull.scm does this with channel files, e.g. with /etc/guix/channels.scm:
>
> (load* file (make-user-module '((guix channels))))
>
> i.e. this way field values are EVAL'd. beside the big can of worms that this opens up, it also means that e.g. the name field must be quoted: (name 'guix).
>
> then at other occurrences of channels, an sexp parser is used to read them, e.g. in the 'dependencies field of a .guix-channel entry. see READ-CHANNEL-METADATA in guix/channels.scm.
>
> here the name field is not EVAL'd, and thus it must be specified without quotes: (name guix).
>
> this leads to an actual issue that channel dependencies don't match up, unless the name is without quotes in the dependencies list specification.

Yes, but that’s okay: the ‘.guix-channel’ file has a syntax that looks
similar but is different from that of ‘~/.config/guix/channels.scm’, as
you explained (and as the manual explains, I think.)  This is on
purpose.

I understand it might look confusing but I’m not sure there’s much we
can do.

Thoughts?

Ludo’.

Previous Next

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