Hi Marius, Marius via <[email protected]> writes:
> Good evening, > > > As far as I understand (I'm probably wrong) /etc/profile is the first > file loaded on the bash start up when requesting a login shell > (interactive or not). > > > At the same time /etc/profile is a system wide "environment > configuration file". For me this means that I should initialize env > variables that are requires by the current system profile > /run/current-system but not anything that is related to any other > profile (for example myuser profile ~.guix-profile). > > > What I understand from the Guix concept and bash files is that any env > variable (PATHS, etc) that need to configured for a specific user > should be inside .bash_profile file. > > > Because of this I don't understand why the /etc/profile includes paths > variables that point to the excuting user $HOME. Shouldn't that be in > the .bash_profile files? Am I missing something? Maybe the reason > because this isn't posible. > > For example why in my /etc/profile I have the following line: > > 'export > INFOPATH=$HOME/.guix-profile/share/info:/run/current-system/profile/share/info' > > It should always work because /etc/profile is only opened with a login > shell, but even so it feels a bit weird to have a reference to $HOME > inside a system wide bash configuration file. What if for example I > changed myuser guix profile name or location from the default one? I think these are variables we set to ensure the default setup works correctly on Guix System. Some variables are set as a workaround to the ancient (yet not fully resolved) bug https://bugs.gnu.org/20255, which is about the system profile not being merged with the user profile. -- Thanks, Maxim
