unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Csepp <raingloom@riseup.net>
Cc: 57118@debbugs.gnu.org
Subject: [bug#57118] [PATCH] gnu: Add linode-cli.
Date: Thu, 01 Sep 2022 10:52:58 +0200	[thread overview]
Message-ID: <878rn35vdh.fsf@gnu.org> (raw)
In-Reply-To: <87v8q728un.fsf@riseup.net> (Csepp's message of "Thu, 01 Sep 2022 03:10:32 +0200")

Hi,

Csepp <raingloom@riseup.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>>> +(define linode-openapi-spec
>>> +  (origin
>>> +    (method url-fetch)
>>> +    (uri "https://www.linode.com/docs/api/openapi.yaml")
>>> +    (sha256
>>> +     (base32
>>> +      "1jcjfnagjihcy03fcmn5sghdf7a80798xjgj1x7z3ncqwd5aggwg"))))

[...]

> I skimmed the OpenAPI spec and couldn't find any mention of how to
> access previous versions.

OK.

> IMHO if there is a build failure, guix refresh -u should take care of
> updating the hash.  It's better than trying to use an outdated API
> description without notifying the user.

I should say I don’t know what this file is used for.  :-)

What I do know is that we should avoid having origins like that above
that are bound to fail.  Perhaps we can find another option?  If the CLI
tools really need the latest version of ‘openapi.yaml’, could they
download it (and possibly cache it) at run time?  Perhaps there are
already provisions for that?

If the tools don’t strictly need the latest version, then hopefully
Linode keeps a copy of this file in a Git repo somewhere?

TIA,
Ludo’.




  reply	other threads:[~2022-09-01  9:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 14:18 [bug#57118] [PATCH] gnu: Add linode-cli raingloom
2022-08-15  8:32 ` Mathieu Othacehe
2022-08-15 11:42 ` [bug#57118] [PATCH v2] " raingloom
2022-08-31 21:33   ` [bug#57118] [PATCH] " Ludovic Courtès
2022-09-01  1:10     ` Csepp
2022-09-01  8:52       ` Ludovic Courtès [this message]
2022-09-01 20:06         ` Csepp
2022-09-02  9:13           ` Ludovic Courtès
2022-09-17 20:13             ` Csepp
2022-09-17 20:24           ` Maxime Devos
2024-04-01  7:53 ` [bug#57118] Linode-cli license Steve George

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=878rn35vdh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=57118@debbugs.gnu.org \
    --cc=raingloom@riseup.net \
    /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).