From: Maxime Devos <maximedevos@telenet.be>
To: Christopher Rodriguez <yewscion@gmail.com>, 53368@debbugs.gnu.org
Subject: bug#53368: .guix-authorizations 'version' field documentation
Date: Thu, 20 Jan 2022 14:07:50 +0100 [thread overview]
Message-ID: <9ad77607fe114f55cc6a0d23e31882faa63f3def.camel@telenet.be> (raw)
In-Reply-To: <99e271fa-7b0e-30f6-0613-57e7942826a3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]
Hi,
Christopher Rodriguez schreef op wo 19-01-2022 om 09:40 [-0500]:
> Hey all,
>
> I've just been able to clone my authenticated personal repository for
> the first time in a few weeks because I was confusing the `version`
> field of `(authorizations …` to be a file version field as opposed to
> the version of the API being used.
>
> For clarity, I'm working on a patch that will edit the section of the
> manual to clearly specify that this is the API version (will submit
> soon). It currently has a comment in the example source that reads
> "current file format version", which lead me to this mistake. Nowhere
> else in the text is the `version` field mentioned.
>
> However, as a Lisper, I feel as though the symbol itself could easily
> be more descriptive by using `api-version` or something similar rather
> than just a generic `version`. It would help prevent other newcomers
> from going through the confusion I've just had.
>
> What do You think?
'version' does denote a file format version. Calling it an API version
is somewhat inaccurate, because it is not a application _programming_
interface -- you can't write Scheme code in .guix-authorizations,
only S-exps that match the file format.
While it is the version of the file format, it is not the version of
the file, which I believe is were the confusion came from?
Also, changing 'version' to 'api-version' would probably prevent old
versions of Guix (that only recognise 'version') from pulling new
versions of Guix (that would have an 'api-version' in their
.guix-authorizations) (untested).
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-20 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c6607218-fc59-ef33-c1d5-7e6b3bfdd254@gmail.com>
2022-01-19 14:40 ` bug#53368: .guix-authorizations 'version' field documentation Christopher Rodriguez
2022-01-19 15:09 ` bug#53368: Patch Christopher Rodriguez
2022-01-20 13:07 ` Maxime Devos [this message]
2022-01-24 14:21 ` bug#53368: .guix-authorizations 'version' field documentation Ludovic Courtès
2022-01-24 14:47 ` bug#53368: guix-authorizations documentation Christopher Rodriguez
2022-03-05 3:47 ` bug#53368: .guix-authorizations 'version' field documentation Maxim Cournoyer
2022-03-23 2:20 ` bug#53368: Missing needed alsa-plugins Christopher Rodriguez
2022-03-23 2:42 ` bug#53368: [PATCH] Amended wording in description of .guix-authorizations file Christopher Rodriguez
2022-03-23 14:42 ` bug#53368: [PATCH v3] Added orca-lang package Christopher Rodriguez
2022-03-23 15:55 ` Maxime Devos
2022-03-23 15:57 ` Maxime Devos
2022-03-23 15:58 ` Maxime Devos
2022-03-23 16:03 ` Maxime Devos
2022-03-23 16:04 ` Maxime Devos
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=9ad77607fe114f55cc6a0d23e31882faa63f3def.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53368@debbugs.gnu.org \
--cc=yewscion@gmail.com \
/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).