From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Best-practice to "develop" a system-config / service?
Date: Thu, 9 Nov 2017 11:36:41 +0100 [thread overview]
Message-ID: <ece63aec-440c-582f-46f6-6abc8e21bd47@crazy-compilers.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
Hi,
TL;DR: How do I get my in-development version of guix into the VM build
with this version?
I made KDE Plasma start up in a VM by adding tons of packages to the
system declaration (to be on the save side). Now for finishing and
providing a nice service declaration I need to strip this list of
packages down to the bare minimum.
Since a vm (sharing the host store) is unacceptable sloooooow, I've
build a vm-image using my development environment ("./pre-inst-env guix
system vm-image …"). Now within the VM-image there is a different
version of guix installed than the in-development one I used for
building the VM. Of course the former one does not know any of the
packages I've just added. So I can't not just run "guix system
reconfigure …".
After some luckless tries I assume the easiest solution would be to get
my in-development version of guix into the VM. How to achieve this?
What I've tried:
0) Using a VM sharing the host store: Here starting Plasma takes 2
minutes, which is not acceptable for series of tests.
1) My first idea was to share my development directory with the VM and
run "./pre-inst-env guix system reconfigure …" from within the VM. This
failed with
./pre-inst-env: …/scripts/guix: /gnu/store/…-profile/bin/guile: bad
interpreter: No such file or directory
Well, yes. within the VM, my external profile is not available :-(
2) Changing the patch in …/scripts/guix into
/run/current-system/profile/bin/guile failed with
/gnu/store/…-libgcrypt-1.8.1/lib/libgcrypt
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: 0xBF773B65.asc --]
[-- Type: application/pgp-keys, Size: 14855 bytes --]
next reply other threads:[~2017-11-09 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 10:36 Hartmut Goebel [this message]
2017-11-10 0:15 ` Best-practice to "develop" a system-config / service? 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
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=ece63aec-440c-582f-46f6-6abc8e21bd47@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
/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.