From: <Ontje.Luensdorf@dlr.de>
To: <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Problem with texlive-default-updmap.cfg
Date: Thu, 31 Mar 2022 06:31:32 +0000 [thread overview]
Message-ID: <87bkxmbpks.fsf@dlr.de> (raw)
In-Reply-To: <87bkxn7gsf.fsf@elephly.net>
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> Commit 2afadeea66e01f6d78e01eee910d2868f27531b8 works around this
> problem by not sharing the same Guile process that was used to launch
> “guix workflow”.
confirmed, my hello world workflow now works, thanks!
> So to avoid “contamination” we now launch a new Guile process with a
> well-known load path. It’s not the prettiest solution, but it works
> around the problem effectively. It is a matter of philosophical debate
> whether the GWL can still be called an “extension” to Guix when we
> aren’t even using the same process and launch an independent Guile
> process, but I’m okay with that because the exploration of this space is
> one of the goals of the GWL :)
I see, the new approach sounds robust to me. Just one question: If I
read the commit right, lib-guix is started as a second process using
system*. Isn't it possible to exec into lib-guix? If I understand the
problem correctly, the host-guix process isn't really required anymore
and can be replaced with lib-guix?
Thanks for fixing the issue & best regards,
Ontje
next prev parent reply other threads:[~2022-03-31 6:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 9:37 Problem with texlive-default-updmap.cfg Ontje.Luensdorf
2022-02-23 15:08 ` Ricardo Wurmus
2022-02-23 22:15 ` Ricardo Wurmus
2022-02-27 17:32 ` Ludovic Courtès
2022-02-27 17:48 ` Ricardo Wurmus
2022-02-28 11:01 ` zimoun
2022-02-28 11:42 ` Ludovic Courtès
2022-02-28 13:17 ` Ricardo Wurmus
2022-02-28 13:15 ` Ricardo Wurmus
2022-03-30 12:32 ` Ricardo Wurmus
2022-03-31 6:31 ` Ontje.Luensdorf [this message]
2022-03-31 7:31 ` Ricardo Wurmus
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkxmbpks.fsf@dlr.de \
--to=ontje.luensdorf@dlr.de \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.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).