From: phodina via <help-guix@gnu.org>
To: help-guix <help-guix@gnu.org>
Subject: Guix pull fails on OS definition
Date: Thu, 12 Aug 2021 15:07:30 +0000 [thread overview]
Message-ID: <XuiNO__2DiHjRIShy3jrWviAo_1W_nySZQXxwBBW4-WrvhHm8vTOJExOoRqalb16GEZ4veXI4kfTi4HAwtA2vFrGfhGEZyLQ15zjGvrL7wo=@protonmail.com> (raw)
Hi Guix,
Till now I've used custom channel for package definition only. However, I want to add to the channel also the definition for the operating system.
The problem is when I run =guix pull= the command fails. The reason is probaly due to the newly added configuration file which returns OS as a result. Without such a file the commands succeeds.
Is there a way to tell Guix not to evaulate such a file?
I looked into the Guix channel and the files are there with the extension tmpl. That however, didn't help.
In the gnu/system.scm file there is at the end expression with note:
"This is not super elegant but we can't pass SYSTEM and TARGET to 'operating-system-derivation'
So is this the right direction to pursue and dig little bit deeper into the store-lift function?
reply other threads:[~2021-08-12 15:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='XuiNO__2DiHjRIShy3jrWviAo_1W_nySZQXxwBBW4-WrvhHm8vTOJExOoRqalb16GEZ4veXI4kfTi4HAwtA2vFrGfhGEZyLQ15zjGvrL7wo=@protonmail.com' \
--to=help-guix@gnu.org \
--cc=phodina@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).