From: Nils Gillmann <ng0@n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 宋文武 <iyzsong@member.fsf.org>, 31237@debbugs.gnu.org
Subject: [bug#31237] [PATCH] gnu: Add runc.
Date: Sun, 22 Apr 2018 23:06:03 +0000 [thread overview]
Message-ID: <20180422230603.gm2u5637w3rkdpvc@abyayala> (raw)
In-Reply-To: <877eoygahy.fsf@gnu.org>
Ludovic Courtès transcribed 1.2K bytes:
> Hello,
>
> 宋文武 <iyzsong@member.fsf.org> skribis:
>
> > * gnu/packages/virtualization.scm (runc): New variable.
>
> Nice!
>
> > +(define-public runc
> > + (package
> > + (name "runc")
> > + (version "1.0.0-rc5")
>
> If the actual release is going to be out soon, I’d be in favor of
> waiting for it; an RC doesn’t sound great. WDYT?
What I wanted to comment earlier from my experience packaging this:
I was advised to follow the docker suggestions, where the dependency
versions are known by recommended commit.
> > + (build-system gnu-build-system)
>
> Would ‘go-build-system’ work better? Or is it something of a hybrid
> (apparently it has makefiles)?
Same question here, since my runc package so far (without testing) just builds,
with go-build-system.
> > + (arguments
> > + '(#:tests? #f ; FIXME: 20/139 tests fail.
>
> Have you looked a bit into them, just to see if it’s one of the usual
> things (/bin/sh, networking, etc.) or if it’s more involved?
>
> > + (invoke "make"))))
>
> Perhaps honor (parallel-job-count).
>
> > + (synopsis "Open container initiative runtime")
> > + (home-page "https://www.opencontainers.org/")
> > + (description
> > + "@command{runc} is a command line client for running applications
> > +packaged according to the Open Container Initiative (OCI) format and is a
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
> An @uref would be nice. :-)
>
> Thanks!
>
> Ludo’.
>
>
>
next prev parent reply other threads:[~2018-04-22 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 12:58 [bug#31237] [PATCH] gnu: Add runc 宋文武
2018-04-22 22:08 ` Ludovic Courtès
2018-04-22 23:06 ` Nils Gillmann [this message]
2018-04-23 3:25 ` 宋文武
2018-04-23 9:41 ` Ludovic Courtès
2018-04-26 1:39 ` bug#31237: " 宋文武
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=20180422230603.gm2u5637w3rkdpvc@abyayala \
--to=ng0@n0.is \
--cc=31237@debbugs.gnu.org \
--cc=iyzsong@member.fsf.org \
--cc=ludo@gnu.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.