From: Attila Lendvai <attila@lendvai.name>
To: Tomas Volf <~@wolfsden.cz>
Cc: Felix Lechner <felix.lechner@lease-up.com>, guix-devel@gnu.org
Subject: Re: Module unavailable on build side
Date: Mon, 15 Jan 2024 00:20:39 +0000 [thread overview]
Message-ID: <2_NlvTw4Q4mx5LcLCTK6OBFEH0ad8y_XpRkdXT15AnZqrJh2c29dZ_mYhfEChAKWmCez3JpFpxABl36Ni_9GGo7CyZymI3eaKeKhhdXPvB8=@lendvai.name> (raw)
In-Reply-To: <ZaPZp-5MhLZlwDDo@ws>
this may help:
https://github.com/attila-lendvai/guix-crypto/blob/main/src/guix-crypto/service-utils.scm#L56
and you should grep for its use in that repo.
w-i-m ensures that the GEXP's that are instantiated in its dynamic extent will "capture" these modules as their dependencies, and i think it also inserts the appropriate use-modules forms at the head of the GEXP's.
but take this all with a grain of salt, because what i understand i decoded on my own from the guix codebase, and the names of these abstractions are rather misleading.
also, i'm using these in the service code that gets compiled for shepherd to be loaded. the environment surrounding the building of packages may behave differently.
HTH,
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“There is no difference between living and learning […] it is impossible and misleading and harmful to think of them as being separate.”
— John Holt (1923–1985)
prev parent reply other threads:[~2024-01-15 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 4:12 Module unavailable on build side Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-14 12:55 ` Tomas Volf
2024-01-15 0:20 ` Attila Lendvai [this message]
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='2_NlvTw4Q4mx5LcLCTK6OBFEH0ad8y_XpRkdXT15AnZqrJh2c29dZ_mYhfEChAKWmCez3JpFpxABl36Ni_9GGo7CyZymI3eaKeKhhdXPvB8=@lendvai.name' \
--to=attila@lendvai.name \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=~@wolfsden.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).