From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50404) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fAO3Z-0007qg-6t for guix-patches@gnu.org; Sun, 22 Apr 2018 19:06:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fAO3W-0007UR-2T for guix-patches@gnu.org; Sun, 22 Apr 2018 19:06:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:56603) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fAO3V-0007UF-VO for guix-patches@gnu.org; Sun, 22 Apr 2018 19:06:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fAO3V-00024E-NS for guix-patches@gnu.org; Sun, 22 Apr 2018 19:06:01 -0400 Subject: [bug#31237] [PATCH] gnu: Add runc. Resent-Message-ID: Date: Sun, 22 Apr 2018 23:06:03 +0000 From: Nils Gillmann Message-ID: <20180422230603.gm2u5637w3rkdpvc@abyayala> References: <20180422125844.15227-1-iyzsong@member.fsf.org> <877eoygahy.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <877eoygahy.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: =?UTF-8?Q?=E5=AE=8B=E6=96=87=E6=AD=A6?= , 31237@debbugs.gnu.org Ludovic Courtès transcribed 1.2K bytes: > Hello, > > 宋文武 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’. > > >