On 03.09.20 14:43, Ulrich Mueller wrote:
>> On Thu, 03 Sep 2020, Florian Schmaus wrote:
>
>> It's not really maintaining the information twice. The information is
>> maintained at a single point: /etc/env.d
>> And from there is is transformed by env-update already into two
>> different
> On Thu, 03 Sep 2020, Florian Schmaus wrote:
> It's not really maintaining the information twice. The information is
> maintained at a single point: /etc/env.d
> And from there is is transformed by env-update already into two
> different formats:
> - /etc/profile.env
> - /etc/csh.env
> And
On 03.09.20 13:30, Ulrich Mueller wrote:
>> On Thu, 03 Sep 2020, Florian Schmaus wrote:
>
>> This commit changes env-update so that, after profile.env has was
>> generated, a systemd user session environment configuration file named
>
>> /usr/lib/environment.d/gentoo-profile-env.conf
>
>>
> On Thu, 03 Sep 2020, Florian Schmaus wrote:
> This commit changes env-update so that, after profile.env has was
> generated, a systemd user session environment configuration file named
> /usr/lib/environment.d/gentoo-profile-env.conf
> is created, if the directory /usr/lib/environment.d
Portage's env-update currently transforms the environment information
from /etc/env.d into /etc/profile.env, which is typically sourced by
every user session, setting up its environment.
However, /etc/profile.env is not sourced by systemd user
services. Instead, for the definition of a systemd
