all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mikhail Kryshen <mikhail@kryshen.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: "Thaddäus Töppen" <thaddaeus.toeppen@gmail.com>, help-guix@gnu.org
Subject: Re: Problem using multiple manifest files
Date: Mon, 22 Oct 2018 21:39:54 +0300	[thread overview]
Message-ID: <87sh0x4yh1.fsf@sh531.localdomain> (raw)
In-Reply-To: <875zxwqts1.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

Chris Marusich <cmmarusich@gmail.com> writes:

> 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!

Thanks! 

> But what is make-user-module doing, and is it necessary?

I looked into the Guix source and reproduced what "guix package -m" does
to load a manifest file.  Make-user-module procedure appear to be used
in Guix to dynamically create modules for running user code.  I could
have simply used "load" here, but then all the files would be loaded in
the same environment and could potentially interfere with each other.

-- 
Mikhail

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

  reply	other threads:[~2018-10-22 18:40 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
2018-10-22 18:39     ` Mikhail Kryshen [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sh0x4yh1.fsf@sh531.localdomain \
    --to=mikhail@kryshen.net \
    --cc=cmmarusich@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=thaddaeus.toeppen@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.