From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Matthew James Kraai" <kraai@ftbfs.org>, <58408@debbugs.gnu.org>
Subject: [bug#58408] [PATCH] gnu: Add doctl.
Date: Mon, 10 Oct 2022 12:01:58 +0100 [thread overview]
Message-ID: <CNI6XGL2DBVK.3P4RA17IA27HH@guix-framework> (raw)
In-Reply-To: <20221010095456.23196-1-kraai@ftbfs.org>
Hey Matthew,
On Mon Oct 10, 2022 at 10:54 AM BST, Matthew James Kraai wrote:
> * gnu/packages/doctl.scm: New file.
> * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
You sure there's no better place to put it than a new file? Maybe
``gnu/packages/admin.scm''?
> + #:use-module (guix download)
Since you're using git-fetch, you shouldn't need this module, right?
> + (arguments
> + `(#:build-flags '(,(string-append "-ldflags=-X github.com/digitalocean/doctl.Label=release"
> + " -X github.com/digitalocean/doctl.Major="
> + (first (string-split version #\.))
> + " -X github.com/digitalocean/doctl.Minor="
> + (second (string-split version #\.))
> + " -X github.com/digitalocean/doctl.Patch="
> + (third (string-split version #\.))))
So, this whole thing would be better formatted with "new style" arguments
(using ``list'' and gexps). Like this:
(arguments
(list #:build-flags
#~(list (string-append ...))
#| et cetera |#))
This would also allow you to remove the unquote in ``,go-1.19''. Note that only
``#:build-flags'' needs the gexp ``#~'' in this arguments list.
> + #:go ,go-1.19
Might be best to put this above build-flags.
> + #:import-path "github.com/digitalocean/doctl/cmd/doctl"
The import-path is usually at the top of the arguments list.
> + #:unpack-path "github.com/digitalocean/doctl"))
And the unpack-path is usually directly after the import-path.
> + (description
> + "doctl provides a unified command line interface to the DigitalOcean API.")
Change ``doctl'' to ``@code{doctl}''.
-- (
next prev parent reply other threads:[~2022-10-10 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 9:54 [bug#58408] [PATCH] gnu: Add doctl Matthew James Kraai
2022-10-10 11:01 ` ( via Guix-patches via [this message]
2022-10-10 13:20 ` Matthew James Kraai
2022-10-10 15:21 ` ( via Guix-patches via
2022-10-11 13:36 ` Matthew James Kraai
2022-10-11 13:41 ` ( via Guix-patches via
2022-10-12 13:08 ` Matthew James Kraai
2022-10-12 15:01 ` ( via Guix-patches via
2022-10-13 1:02 ` Matthew James Kraai
2022-10-13 6:11 ` ( via Guix-patches via
2022-10-21 3:38 ` Matthew James Kraai
2022-10-23 13:07 ` bug#58408: " Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CNI6XGL2DBVK.3P4RA17IA27HH@guix-framework \
--to=guix-patches@gnu.org \
--cc=58408@debbugs.gnu.org \
--cc=kraai@ftbfs.org \
--cc=paren@disroot.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.