unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: 57118@debbugs.gnu.org
Subject: [bug#57118] [PATCH] gnu: Add linode-cli.
Date: Mon, 15 Aug 2022 10:32:14 +0200	[thread overview]
Message-ID: <87y1vpgb5d.fsf@gnu.org> (raw)
In-Reply-To: <20220810141843.21051-1-raingloom@riseup.net> (raingloom@riseup.net's message of "Wed, 10 Aug 2022 16:18:43 +0200")


Hey,

> * gnu/packages/python-xyz.scm (linode-cli): New variable.

You also need to mention the linode-openapi-spec variable.

> +    (synopsis "Tool for managing Linode resources")
> +    (home-page "https://www.linode.com/docs/products/tools/cli/")

These are usually at the end of the package definition.

> +                               (assoc-ref inputs
> +                                          "linode-openapi-spec")

It would be preferable to use the gexp mechanism.

> +                                   (assoc-ref outputs "out")

Here too.

> +     "A wrapper around the Linode API, which gives you the ability to manage
> +your Linode account from the command line. Almost any task that can be done
> +through the Cloud Manager can also be performed through the CLI.")

This package provides a wrapper around Linode API which gives the
ability to manage Linode accounts from the command line.  Almost ...

Sentences must be separated by two spaces.

Could you please send a v2?

Thanks,

Mathieu




  reply	other threads:[~2022-08-15  8:33 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 [this message]
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
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=87y1vpgb5d.fsf@gnu.org \
    --to=othacehe@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).