FS#49320 - [pam] Set basic environment variables in /etc/environment, not (just) in /etc/profile

Attached to Project: Arch Linux
Opened by Sander Maijers (sanmai-NL) - Friday, 13 May 2016, 10:39 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 20 September 2023, 03:10 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When the user changes his/her shell on current Arch Linux to one doesn't/cannot read /etc/profile (e.g. fish), the base PATH environment variable won't be set correctly without tricks.

Actual behavior:
PATH is now only set in /etc/profile (with filesystem 2015.09-1) and not in /etc/environment (with pam 1.2.1-3).

Desired behavior:
Why is e.g. PATH not (also) in /etc/environment? Suppose you want to keep something like PATH="/usr/local/sbin:/usr/local/bin:/usr/bin" around in /etc/profile, any shell that does read /etc/profile could still process /etc/profile.d as before, setting the base PATH conditional on PATH it being set already, using PATH="${PATH:-/usr/local/sbin:/usr/local/bin:/usr/bin}"
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 20 September 2023, 03:10 GMT
Reason for closing:  Won't implement
Additional comments about closing:  No interest from PM's. Setting up fish is covered in the wiki.
Comment by Matthias Dienstbier (fs4000) - Tuesday, 17 May 2016, 05:29 GMT
Maybe related with  FS#47884 .
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...