Search Criteria
Package Details: xdg-base-dir-env 1.0.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/xdg-base-dir-env.git (read-only, click to copy) |
|---|---|
| Package Base: | xdg-base-dir-env |
| Description: | Default XDG Base Directory environment variables. |
| Upstream URL: | https://wiki.archlinux.org/title/XDG_Base_Directory |
| Submitter: | perigoso |
| Maintainer: | perigoso |
| Last Packager: | perigoso |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2023-04-12 22:02 (UTC) |
| Last Updated: | 2023-04-12 22:02 (UTC) |
Latest Comments
perigoso commented on 2023-04-26 14:29 (UTC)
Yes compliant software should not need this, but not everything is compliant and so sometimes we need custom user configurations, these provide convenient variables for such configurations.
/usr/lib/environment.d is only evaluated by systemd services yes, but most sane environments spawned from systemd export the systemd environment to the user, and when it doesnt the user can configure that behavior, there isn't a single place where we can configure enviorenment that will be available everywhere by default, environment.d is the sanest place IMO
In the end this is for the user, no software will "depend on these environment variables being set", when they are not available software should just fallback to the defaults which are the same, no harm done
qubidt commented on 2023-04-12 22:46 (UTC)
Not a good idea, IMO. Any software that recognize these variables should already be using those values as the default (per spec), and
/usr/lib/environment.dis only evaluated for systemd user services, programs started from the login shell won't receive that config. So depending on these environment variables being set is not wise