From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: how to create and test a new service definition Date: Sat, 13 May 2017 22:06:18 +0200 Message-ID: <878tm0zflx.fsf@gnu.org> References: <87vap4zupo.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d9dJ3-0002hM-6y for guix-devel@gnu.org; Sat, 13 May 2017 16:06:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d9dJ0-0004U7-3P for guix-devel@gnu.org; Sat, 13 May 2017 16:06:25 -0400 In-Reply-To: (Vincent Legoll's message of "Sat, 13 May 2017 17:24:13 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Vincent Legoll Cc: guix-devel Vincent Legoll skribis: >> The best way to test your code is to write an =E2=80=98operating-system= =E2=80=99 >> declaration that uses the new service and to instantiate it in a VM with >> =E2=80=98guix system vm=E2=80=99. > > Should that be working properly (out-of-the-box) when you're already in > a qemu VM (recursive virtualization) ? > > I ask because I'm getting: > > [...] > ERROR: qemu failed "qemu-system-x86_64" What were the lines above this one? This tool tries to use KVM if it seems available. Maybe in your case it =E2=80=9Cseems=E2=80=9D to be avail= able (as in /dev/kvm exists) but is actually unusable? >> Once you=E2=80=99ve done that, you can also write an automated test for = the new >> service; see . > > I'm far from there, I have a *really* hard time getting back to guixsd. F= or > instance it took me very long time to find back the GUIX_PACKAGE_PATH > env var. This looks under-documented, or I don't understand how one is to > work on custom or new packages, etc... =E2=80=98GUIX_PACKAGE_PATH=E2=80=99 is documented at . The workflow for defining packages is described at , and that for contributing them is at . There=E2=80=99s probably room for improvement though. What changes/additio= ns would you suggest? > guix edit is throwing me : > E166: Can't open linked file for writing This error does not come from =E2=80=98guix edit=E2=80=99, but maybe from y= our editor. As for why the file is read-only, see . HTH, Ludo=E2=80=99.