Emmanuel Medernach writes:
>> I pulled the same commit on the VM that the one obtained
>> with "guix describe" but it still recompiles my local
>> packages with "guix build". Did I forget something ?
>>
>
>
> I mean it does not download from my substitute server.
Did you authorize
> I pulled the same commit on the VM that the one obtained
> with "guix describe" but it still recompiles my local
> packages with "guix build". Did I forget something ?
>
I mean it does not download from my substitute server.
I have another question: How to query the output paths
On Wed, Jun 3, 2020 at 5:23 PM Marius Bakke wrote:
>
> '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.
>
>
Thanks it works
> The reason 'guix build foo' gives a different
s 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 upda
"guix build" to list store
directories from package names but it tries
instead to recompile them even though they are
already installed.
How to properly export local definitions in the
virtual machine image ?
Best regards,
Emmanuel Medernach
