[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: native-search-paths and shepherd services (help wanted)

From: Ludovic Courtès
Subject: Re: native-search-paths and shepherd services (help wanted)
Date: Tue, 11 Feb 2020 15:40:29 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)


Brice Waegeneire <address@hidden> 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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]