From: Chris Marusich <cmmarusich@gmail.com>
To: Mikhail Kryshen <mikhail@kryshen.net>
Cc: help-guix@gnu.org
Subject: Re: Problem using multiple manifest files
Date: Sat, 20 Oct 2018 12:53:34 -0700 [thread overview]
Message-ID: <875zxwqts1.fsf@gmail.com> (raw)
In-Reply-To: <878t3162vu.fsf@seashell.localdomain> (Mikhail Kryshen's message of "Sat, 13 Oct 2018 22:52:05 +0300")
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
Mikhail Kryshen <mikhail@kryshen.net> writes:
> (use-modules (srfi srfi-1)
> ((guix ui) #:select (make-user-module)))
>
> (define (load-manifest file)
> ;; Load manifest file in a fresh module with necessary imports.
> (let ((module (make-user-module '((guix profiles) (gnu)))))
> (save-module-excursion
> (lambda _
> (set-current-module module)
> (load (canonicalize-path file))))))
Neat example! But what is make-user-module doing, and is it necessary?
I checked in the Guix source and found that this procedure uses the
procedure make-fresh-user-module, which comes from the (ice-9 boot)
module and is not documented in the Guile Reference manual. I stopped
investigating when I checked the ice-9 source code and found that it did
not contain an immediately helpful docstring or comment. It feels like
maybe make-fresh-user-module ought to be documented in "(guile) Module
System Reflection", but it isn't. Unfortunately, I don't have time
right now to dig deeper.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-10-20 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 21:50 Problem using multiple manifest files Thaddäus Töppen
2018-10-13 4:08 ` Ricardo Wurmus
2018-10-13 19:52 ` Mikhail Kryshen
2018-10-15 12:10 ` Ludovic Courtès
2018-10-20 19:53 ` Chris Marusich [this message]
2018-10-22 18:39 ` Mikhail Kryshen
2018-10-23 8:07 ` Chris Marusich
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=875zxwqts1.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=mikhail@kryshen.net \
/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).