Hi Ludo,
On Mon, 22 Feb 2021 at 23:41, Ludovic Courtès wrote:
> As you point out, we can have the ‘transformations’ property of manifest
> entries created automatically by default; the patch below does that.
> That way, the ‘transformations’ property is saved by default whether you
> use a manif
Hi,
zimoun skribis:
> Hi Ludo,
>
> On Thu, 11 Feb 2021 at 00:01, Ludovic Courtès wrote:
>
>> That’s because when using ‘-m’, transformations are not recorded.
>
> Yes. The question is: is it a conscientious choice or a missing
> feature?
[...]
> For example, ’package->manifest-entry*’ is "Li
Hi Ludo,
On Thu, 11 Feb 2021 at 00:01, Ludovic Courtès wrote:
> That’s because when using ‘-m’, transformations are not recorded.
Yes. The question is: is it a conscientious choice or a missing
feature?
It makes sense to save the transformations from a manifest, IMHO. But
it is not clear wh
Hi,
zimoun 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/pr
Hi,
If the transformations are in the manifest.scm file, then they are
lost. For example, consider:
--8<---cut here---start->8---
$ guix package \
-p /tmp/profile-cli \
-i python python-numpy \
hello --with-c-toolchain=hello=gcc-toolchain@