From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Legoll Subject: Re: how to create and test a new service definition Date: Sat, 13 May 2017 17:24:13 +0200 Message-ID: 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]:34778) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d9Yu1-0001yf-Ao for guix-devel@gnu.org; Sat, 13 May 2017 11:24:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d9Yu0-0001IU-3M for guix-devel@gnu.org; Sat, 13 May 2017 11:24:17 -0400 In-Reply-To: <87vap4zupo.fsf@gnu.org> 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: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: guix-devel > 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" [...] > Once you=E2=80=99ve done that, you can also write an automated test for t= he new > service; see . I'm far from there, I have a *really* hard time getting back to guixsd. For 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... guix edit is throwing me : E166: Can't open linked file for writing Looks like I'm missing something big. --=20 Vincent Legoll