From: "Ludovic Courtès" <ludo@gnu.org>
To: Brice Waegeneire <brice@waegenei.re>
Cc: guix-devel@gnu.org,
Guix-devel <guix-devel-bounces+brice+lists=waegenei.re@gnu.org>
Subject: Re: native-search-paths and shepherd services (help wanted)
Date: Tue, 11 Feb 2020 15:40:29 +0100 [thread overview]
Message-ID: <87ftfh192a.fsf@gnu.org> (raw)
In-Reply-To: <e6f9244a8e73cb7f6032dc527408d44d@waegenei.re> (Brice Waegeneire's message of "Sat, 08 Feb 2020 19:39:59 +0000")
Hello,
Brice Waegeneire <brice@waegenei.re> skribis:
> On 2020-02-08 19:10, Jonathan Frederickson wrote:
>> I'm still not quite sure I have a good understanding of when
>> 'native-search-paths' applies and when it doesn't, but... at least
>> setting the env var directly seems to work in this case.
>
> I just learned about native-search-paths when looking into your issue
> so I may be off about how it works...
> What I understand is that native-search-paths add an entry to your
> /etc/profile when installed - for your default user profile it's
> $HOME/.guix-profile/etc/profile. In our case, when installed, minetest
> sets the environment variable MINETEST_SUBGAME_PATH so the binary know
> where to looks for the games. But when called directly, as it's the
> case in a shepherd service, the /etc/profile file isn't sourced so the
> environment variable isn't set. That's why we need to set it manually
> in the service.
Search paths are only used when building a profile, which is not the
case here.
I suppose you’d have to explicitly pass #:environment-variables to
‘make-forkexec-constructor’ to get the desired effect.
HTH,
Ludo’.
prev parent reply other threads:[~2020-02-11 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 9:06 native-search-paths and shepherd services (help wanted) Jonathan Frederickson
2020-02-08 10:28 ` Brice Waegeneire
2020-02-08 19:10 ` Jonathan Frederickson
2020-02-08 19:39 ` Brice Waegeneire
2020-02-11 14:40 ` Ludovic Courtès [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=87ftfh192a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=brice@waegenei.re \
--cc=guix-devel-bounces+brice+lists=waegenei.re@gnu.org \
--cc=guix-devel@gnu.org \
/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).