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

Previous Next

Package: guix;

Reported by: Danny Milosavljevic <dannym <at> scratchpost.org>

Date: Wed, 15 May 2019 15:33:02 UTC

Severity: normal

To reply to this bug, email your comments to 35751 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#35751; Package guix. (Wed, 15 May 2019 15:33:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Danny Milosavljevic <dannym <at> scratchpost.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Wed, 15 May 2019 15:33:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: <bug-guix <at> gnu.org>
Subject: "guix environment -s" doesn't set %current-system in gnu/packages
Date: Wed, 15 May 2019 17:32:11 +0200
[Message part 1 (text/plain, inline)]
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?

[Message part 2 (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#35751; Package guix. (Sat, 18 May 2019 17:20:01 GMT) Full text and rfc822 format available.

Message #8 received at 35751 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 35751 <at> debbugs.gnu.org
Subject: Re: bug#35751: "guix environment -s" doesn't set %current-system in
 gnu/packages
Date: Sat, 18 May 2019 19:19:40 +0200
Hi Danny,

Danny Milosavljevic <dannym <at> 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’.




This bug report was last modified 6 years and 25 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.