From: Ricardo Wurmus <rekado@elephly.net>
To: Alex Kost <alezost@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: overriding essential-services
Date: Tue, 15 Aug 2017 22:05:38 +0200 [thread overview]
Message-ID: <87r2wcfvfx.fsf@elephly.net> (raw)
In-Reply-To: <87y3qohiap.fsf@gmail.com>
Alex Kost <alezost@gmail.com> writes:
> Ricardo Wurmus (2017-08-11 22:26 +0200) wrote:
>
>> Hi Guix,
>>
>> I want to make sure that /etc/environment includes GUILE_LOAD_PATH and
>> GUILE_LOAD_COMPILED_PATH, because that’s needed for offloading.
>> “/etc/environment” is created by the “session-environment-service”
>> service, which is part of “essential-services”. It is not part of
>> %base-services, so I cannot catch it with “modify-services” and extend
>> it.
>>
>> How would I go about extending it?
>
> There is probably no convenient way now.
>
>> For now I’ll use ~/.ssh/environment and “PermitUserEnvironment=yes”, but
>> I think it would anyway be good to have a mechanism to easily change the
>> contents of /etc/environment.
>
> IFIUC the intention of <https://bugs.gnu.org/27155> is to provide the
> extension facility for any service.
I don’t know… I never quite warmed up to the implementation. It looks
much too powerful for something as simple as e.g. overwriting
/etc/environment.
Maybe “session-environment-service-type” is an outlier here anyway. I
see the utility of 27155 for the other services, but using it for
“session-environment-service-type” really seems wrong. Maybe we can
move it to %base-services?
And maybe we could avoid essential-services altogether and make these
services explicit, so that they can be modified with “modify-services”.
Right now they are special in that they are always added to whatever
services the user defines.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-08-15 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 20:26 overriding essential-services Ricardo Wurmus
2017-08-12 16:17 ` Alex Kost
2017-08-15 20:05 ` Ricardo Wurmus [this message]
2017-08-19 18:41 ` Alex Kost
2017-08-22 9:46 ` Ludovic Courtès
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=87r2wcfvfx.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=alezost@gmail.com \
--cc=help-guix@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.
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).