Jishnu Kaiwar <jishnukai...@gmail.com> writes:
I tried $HOME/.pam_environment on the wiki's recommendation [1]
with
the
syntax from pam_env.conf(5) but this didn't set the variables at
all
(tested with a simple echo $GOPATH, echo $PATH).
It seems Arch Linux's wiki claims that this is not read anymore
[2],
In any case, the pam_env(8) man page says that user environment
files are not only deprecated, but:
will be removed completely at some point in the future.
So once this discussion has determined the appropriate
alternative, i'll update that Knowledge Base page on the Gentoo
wiki accordingly.
I tried their suggested method of using systemd user environment
variables based on environment.d(5). Here I had some success in
setting
some environment variables such as $GOPATH, but it did not
change the
$PATH as I desired; systemctl --user reload-daemon and
show-environment
to verify. This is odd because the man page has setting $PATH as
an
example.
Has anybody else run into this issue? If so what do you do
instead. I
am
now sourcing ~/.profile from my ~/.bashrc but this seems not
perfectly
"correct".
Well, one factor: are you using a display manager, like GDM? Or
are you starting your GNOME session from the console?
(i might not be able to offer any help, as i use OpenRC, not
systemd, and don't use a display manager - over time i've found
them to be more trouble than they're worth for my use-case. i
start my Wayland sessions - previously Sway, currently Wayfire -
from the console, and i set the environment for my login session,
including PATH, in ~/.zprofile, Zsh's equivalent of
~/.bash_profile.)
Alexis.
