unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, ison <ison@airmail.cc>
Cc: guix-devel@gnu.org
Subject: Re: Discrepancy between manual and channels.scm
Date: Fri, 26 Mar 2021 08:54:56 +0100	[thread overview]
Message-ID: <86pmzmbb8v.fsf@gmail.com> (raw)
In-Reply-To: <875z1l7o7q.fsf@gnu.org>

Hi,

On Sat, 20 Mar 2021 at 18:02, Ludovic Courtès <ludo@gnu.org> wrote:
> ison <ison@airmail.cc> skribis:
>
>> Under "6.7 Declaring Channel Dependencies" the examples show names being
>> quoted, such as (name 'some-collection) however this causes guix pull to
>> fail. I don't remember the exact error but it was failing the "match"
>> statement under "resolve-dependencies" in "guix/channels.scm".
>>
>> (name "some-collection") also fails.
>> (name some-collection) succeeds, without any quoting.
>
> Oops you’re right; I’ll push a fix to the manual shortly.

Indeed, it can be confusing to have:

  (name some-collection)

where elsewhere it is quoted.  Related to below, since it is data, does
you make sense to have (name “some-collection”) for .guix-channel and a
’string->symbol’ somewhere.


>> I'm not sure if it's the manual which needs fixing or the code, but
>> specifying the name without quoting would be inconsistent with how
>> channel names are declared in ~/.config/guix/channels.scm.
>
> It’s necessarily different because ‘.guix-channel’ is data whereas
> ‘channels.scm’ is code.

Right, option ’--channels/-C’ of “guix pull” says: «file must contain
Scheme code» then section “Specifying Additional Channels” says «Note
that the snippet above is (as always!) Scheme code».

However, what is maybe less clear is that ’.guix-channel’ is data.  Even
if it is often said «meta-data file .guix-channel».  Maybe the “meta” is
confusing.  Why simply not say «data file».  Or «meta-data file
.guix-channel (which is not code)».

Well, it is confusing because code is data. :-)  And all is using
parenthesis.  And the ’.guix-channel’ looks very similar as channels.scm.

Cheers,
simon


  reply	other threads:[~2021-03-26  8:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  1:15 Discrepancy between manual and channels.scm ison
2021-03-20 17:02 ` Ludovic Courtès
2021-03-26  7:54   ` zimoun [this message]
2021-03-27  3:23   ` Ozhap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86pmzmbb8v.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ison@airmail.cc \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).