Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#54752 - [perl] user systemd units do not know about perl PATH changes
Attached to Project:
Arch Linux
Opened by Alex (zreeon) - Monday, 10 July 2017, 09:04 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 10 July 2017, 15:03 GMT
Opened by Alex (zreeon) - Monday, 10 July 2017, 09:04 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 10 July 2017, 15:03 GMT
|
DetailsDescription:
Units started as a systemd user (via systemctl --user start something.service) don't know about the changes to PATH that perl makes. Steps to reproduce: 1. systemctl --user show-environment Does not have the modifications to PATH that perl makes. |
This task depends upon
I guess I'm confused as to why perl sets up the PATH for shells like bash/zsh but not for the systemd user environment.
Also, the "fix" listed in that section of the wiki does not work if the systemd services have been "enabled." I guess they run before .bash_profile is sourced?
Systemd essentially implements its own minimal PATH (an upstream choice), so /etc/profile certainly counts as a customized PATH.