unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Christopher Rodriguez <yewscion@gmail.com>, 53368@debbugs.gnu.org
Subject: bug#53368: .guix-authorizations 'version' field documentation
Date: Mon, 24 Jan 2022 15:21:49 +0100	[thread overview]
Message-ID: <874k5tusci.fsf@gnu.org> (raw)
In-Reply-To: <9ad77607fe114f55cc6a0d23e31882faa63f3def.camel@telenet.be> (Maxime Devos's message of "Thu, 20 Jan 2022 14:07:50 +0100")

Hi,

Maxime Devos <maximedevos@telenet.be> skribis:

> '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).

I agree with everything you wrote.

Christopher, with this in mind, do you think we need a sentence or two
in the manual to clarify what the ‘version’ field is about?

Thanks,
Ludo’.




  reply	other threads:[~2022-01-24 14:24 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   ` bug#53368: .guix-authorizations 'version' field documentation Maxime Devos
2022-01-24 14:21     ` Ludovic Courtès [this message]
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=874k5tusci.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53368@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    --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).