bug#35751: "guix environment -s" doesn't set %current-system in gnu/packages

bug#35751: "guix environment -s" doesn't set %current-system in gnu/packages

[Danny Milosavljevic]

[-- Attachment #1: Type: text/plain, Size: 358 bytes --]

Hi,

when doing "guix environment -s armhf-linux", apparently it doesn't set
%current-system to "armhf-linux" for packages in gnu/packages at toplevel
context.

That would be convenient for development, f.e. instead of "guix build" I often
use "guix environment" inside the git checkout of the package.  In this case
it's differing.

Should it?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

bug#35751: "guix environment -s" doesn't set %current-system in gnu/packages

[Ludovic Courtès]

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> when doing "guix environment -s armhf-linux", apparently it doesn't set
> %current-system to "armhf-linux" for packages in gnu/packages at toplevel
> context.

Correct.  That’s the way it’s meant to work: the initial value of
‘%current-system’ when files get loaded should not matter.

> That would be convenient for development, f.e. instead of "guix build" I often
> use "guix environment" inside the git checkout of the package.  In this case
> it's differing.

Package definitions should refer to ‘%current-system’ only from within
the dynamic extent of a thunked field.

For example, if a package refers to ‘%current-system’ from ‘arguments’,
or from a procedure called from ‘arguments’, everything is fine:
‘%current-system’, at that point, will be bound to whatever was selected
with ‘-s’.

Does that make sense?

Thanks,
Ludo’.