all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Best-practice to "develop" a system-config / service?
Date: Mon, 13 Nov 2017 11:44:46 +0100	[thread overview]
Message-ID: <87bmk6v4o1.fsf@gnu.org> (raw)
In-Reply-To: <4979aced-2139-7994-9b0f-cf8d7b20f2f5@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 12 Nov 2017 16:50:26 +0100")

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> Am 11.11.2017 um 14:51 schrieb Ludovic Courtès:
>> Well, I’ve always used the above approach to test system services as I
>> worked on them, and the 10–30 seconds it took for ‘guix system vm’ to
>> complete as I tweak the service were never that much of a hindrance to
>> me.
>
> JFYI: Building a new VM takes more than 90 seconds on my system.

With ‘guix system vm’, right?  I guess it also depends on the number of
things that need to be built, but 90 seconds remains acceptable IMO.

Ludo’.

  reply	other threads:[~2017-11-13 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 10:36 Best-practice to "develop" a system-config / service? Hartmut Goebel
2017-11-10  0:15 ` Marius Bakke
2017-11-11 11:31 ` Ludovic Courtès
2017-11-11 13:05   ` Speed of qemu VM sharing the store (was: Best-practice to "develop" a system-config / service?) Hartmut Goebel
2017-11-11 13:45     ` Speed of qemu VM sharing the store Ludovic Courtès
2017-11-12 10:19       ` Hartmut Goebel
2017-11-11 13:22   ` Best-practice to "develop" a system-config / service? Hartmut Goebel
2017-11-11 13:51     ` Ludovic Courtès
2017-11-12 15:50       ` Hartmut Goebel
2017-11-13 10:44         ` Ludovic Courtès [this message]
2017-11-18  9:09           ` Hartmut Goebel

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=87bmk6v4o1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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.