From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Best-practice to "develop" a system-config / service? Date: Sat, 11 Nov 2017 14:51:55 +0100 Message-ID: <87tvy0hqis.fsf@gnu.org> References: <87po8phx0d.fsf@gnu.org> <132a3313-27ac-210c-8156-41fa3e06d46f@crazy-compilers.com> 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]:57748) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eDWCW-00025P-Gl for guix-devel@gnu.org; Sat, 11 Nov 2017 08:52:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eDWCV-0006Uo-Jj for guix-devel@gnu.org; Sat, 11 Nov 2017 08:52:00 -0500 Received: from hera.aquilenet.fr ([2a01:474::1]:43170) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eDWCV-0006T9-C6 for guix-devel@gnu.org; Sat, 11 Nov 2017 08:51:59 -0500 In-Reply-To: <132a3313-27ac-210c-8156-41fa3e06d46f@crazy-compilers.com> (Hartmut Goebel's message of "Sat, 11 Nov 2017 14:22:59 +0100") 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: Hartmut Goebel Cc: guix-devel Hartmut Goebel skribis: > Am 11.11.2017 um 12:31 schrieb Ludovic Court=C3=A8s: >> I think all you want, to test your KDE service, is to: >> >> 1. Write an OS config that uses the service. >> >> 2. Run =E2=80=9C./pre-inst-env guix system vm that-config.scm=E2=80=9D= , run the VM, >> and check if it works. >> >> That=E2=80=99s really all it takes to develop and test a system service. > > Not in my case. Plasma heavily relies on plugins and such. I have added > about 50 package to the system configuration to make Plasma start. Now I > need [1] to iterately remove (and re-add) packages (not services!) to > learn what are actual the minimum requirements. > > Creating a new VM for each iteration is *much* too time-consuming =E2=80= =93 no > matter if using "vm-image" or "vm" =E2=80=93, let alone since this requir= ed to > reboot the machine each time. Even if I would try to write a test-case > for this [2], each cycle would take too much time. Well, I=E2=80=99ve always used the above approach to test system services a= s I worked on them, and the 10=E2=80=9330 seconds it took for =E2=80=98guix sys= tem vm=E2=80=99 to complete as I tweak the service were never that much of a hindrance to me. But yeah, I understand you=E2=80=99re using =E2=80=98vm-image=E2=80=99, so = it=E2=80=99s a different story since =E2=80=98vm-image=E2=80=99 takes ages. Now, it seems to me that the workflow you describe has become this complicated just because of the slowness of Plasma in the VM. To me that=E2=80=99s something worth investigating. Granted a VM with a 9p-mount= ed store is slower than a bare metal system, but it shouldn=E2=80=99t be this = slow. Something=E2=80=99s wrong. > On a Fedora-like system I would simply 'rpm -e PACKAGENAME`. > Unfortunately guix is not able to uninstall a package it does not know > (see ). It cannot uninstall a propagated package, if that=E2=80=99s what you mean. Ludo=E2=80=99.