[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unexpected --export-manifest with simple transformations
From: |
Ludovic Courtès |
Subject: |
Re: Unexpected --export-manifest with simple transformations |
Date: |
Thu, 11 Feb 2021 00:01:46 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> So far, so good. Then let use this manifest to create a profile.
>
> $ guix package -p /tmp/profile-exported -m /tmp/manifest.scm
>
> and the issue is that ’/tmp/profile-exported/manifest’ does not contain
> the transformation. Other said:
>
> $ guix package -p /tmp/profile-exported --export-manifest
> ;; This "manifest" file can be passed to 'guix package -m' to reproduce
> ;; the content of your profile. This is "symbolic": it only specifies
> ;; package names. To reproduce the exact same profile, you also need to
> ;; capture the channels being used, as returned by "guix describe".
> ;; See the "Replicating Guix" section in the manual.
>
> (specifications->manifest
> (list "hello" "python-numpy" "python"))
That’s because when using ‘-m’, transformations are not recorded.
‘--export-manifest’ can be thought of as a disassembler; in this case,
it lacks debug info to perform better.
HTH,
Ludo’.