From: Timmy Douglas via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 52174@debbugs.gnu.org
Subject: [bug#52174] [PATCH v2 2/6] gnu: add conmon
Date: Tue, 21 Dec 2021 14:42:16 -0800 [thread overview]
Message-ID: <87o859zik7.fsf@timmydouglas.com> (raw)
In-Reply-To: <87wnjzjtk2.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Timmy Douglas <mail@timmydouglas.com> skribis:
>
>> * gnu/packages/containers.scm: add conmon
>
> [...]
>
>> + (source
>> + (origin
>> + (method git-fetch)
>> + (uri (git-reference
>> + (url "https://github.com/containers/conmon")
>> + (commit (string-append "v" version))))
>> + (sha256
>> + (base32 "1sxpbm01g4xak4kqwvk45gmzr6n9bjzlfp1j85wyz8rj2hg2x4rm"))
>> + (file-name (git-file-name name version))))
>> +
>> + (build-system gnu-build-system)
>
> Nitpick: you can remove the empty line.
ok. I think guix lint outputted that way or maybe I already had it like that?
>> + (arguments
>> + `(#:make-flags (list ,(string-append "CC=" (cc-for-target))
>> + (string-append "PREFIX=" %output))
>> + #:tests? #f ; currently broken as go tries to use network
>
> Indentation is off.
emacs really likes to indent it like that. I wonder if I'm missing
something in my setup.
I'll take a look at just skipping network tests rather than avoiding
them altogether.
next prev parent reply other threads:[~2021-12-21 22:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 6:46 [bug#52174] [PATCH] gnu: Add podman Timmy Douglas via Guix-patches via
2021-12-18 17:57 ` Ludovic Courtès
2021-12-19 4:58 ` [bug#52174] [PATCH v2 1/6] gnu: add crun Timmy Douglas via Guix-patches via
[not found] ` <875yrjl8a5.fsf@gnu.org>
2021-12-21 20:17 ` Timmy Douglas via Guix-patches via
2021-12-24 15:23 ` Ludovic Courtès
2021-12-25 0:22 ` Timmy Douglas via Guix-patches via
2022-01-01 18:11 ` bug#52174: [PATCH] gnu: Add podman Ludovic Courtès
2022-01-01 19:59 ` [bug#52174] " Timmy Douglas via Guix-patches via
2022-01-03 11:14 ` Ludovic Courtès
2021-12-19 4:58 ` [bug#52174] [PATCH v2 2/6] gnu: add conmon Timmy Douglas via Guix-patches via
[not found] ` <87wnjzjtk2.fsf@gnu.org>
2021-12-21 22:42 ` Timmy Douglas via Guix-patches via [this message]
2021-12-24 15:25 ` Ludovic Courtès
2021-12-19 4:58 ` [bug#52174] [PATCH v2 3/6] gnu: add libslirp Timmy Douglas via Guix-patches via
[not found] ` <871r27l87f.fsf@gnu.org>
2021-12-21 22:37 ` Timmy Douglas via Guix-patches via
2021-12-24 15:24 ` Ludovic Courtès
2021-12-19 4:58 ` [bug#52174] [PATCH v2 4/6] gnu: add slirp4netns Timmy Douglas via Guix-patches via
2021-12-19 4:58 ` [bug#52174] [PATCH v2 5/6] gnu: add cni-plugins Timmy Douglas via Guix-patches via
2021-12-19 4:58 ` [bug#52174] [PATCH v2 6/6] gnu: add podman Timmy Douglas via Guix-patches via
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=87o859zik7.fsf@timmydouglas.com \
--to=guix-patches@gnu.org \
--cc=52174@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mail@timmydouglas.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 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.