Hi Danny, Danny Milosavljevic <[email protected]> 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’.
