From: Marius Bakke <marius@gnu.org>
To: Emmanuel Medernach <emmanuel.medernach@gmail.com>,
help-guix <help-guix@gnu.org>
Subject: Re: Local definitions and Virtual machine image
Date: Wed, 03 Jun 2020 17:23:28 +0200 [thread overview]
Message-ID: <87k10ouqa7.fsf@gnu.org> (raw)
In-Reply-To: <CAC_pKx_tz2AeWfn50Kd7nKN57e6emog6Qnbm4jCMTDAXAc6kXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
Emmanuel Medernach <emmanuel.medernach@gmail.com> writes:
> Hello Guixers !
>
> I created an image with 'guix system vm-image'
> which contains local defined packages. These
> packages are present on the Virtual Machine
> however they are not listed with 'guix package
> --list-installed'.
'guix package -I' only lists packages that are installed to the user
profile. Use 'guix package -p /run/current-system/profile -I' to see
system-installed packages.
> As I need to customize
> LD_LIBRARY_PATH, I use "guix build" to list store
> directories from package names but it tries
> instead to recompile them even though they are
> already installed.
The reason 'guix build foo' gives a different result is because you have
not run 'guix pull', so you are using the "guix snapshot" from
gnu/packages/package-management.scm, which is on a fixed commit.
Whereas when you built the VM, you were likely using a newer version of
Guix.
> How to properly export local definitions in the
> virtual machine image ?
There are a couple of ways around this. One is to run 'make
update-guix-package' in the Guix source tree to update the Guix
snapshot, and use './pre-inst-env' when generating the VM. It requires
a Guix development setup though.
Another is to look at the commit that was used to generate the VM in
/run/current-system/provenance and run 'guix pull --commit=that-commit'.
Perhaps 'guix system vm-image' could learn a '--update-guix-snapshot' to
automatically update the "system guix". Someone would have to implement
it first though. :-)
HTH,
Marius
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-06-03 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 12:17 Local definitions and Virtual machine image Emmanuel Medernach
2020-06-03 15:23 ` Marius Bakke [this message]
2020-06-05 14:54 ` Emmanuel Medernach
2020-06-05 15:12 ` Emmanuel Medernach
2020-07-25 15:12 ` Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k10ouqa7.fsf@gnu.org \
--to=marius@gnu.org \
--cc=emmanuel.medernach@gmail.com \
--cc=help-guix@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).