You are not logged in.
- Topics: Active | Unanswered
#1 2021-10-15 12:19:51
- laichiaheng
- Member
- Registered: 2017-02-12
- Posts: 297
Why not put all the PipeWire config files to /etc/pipewire?
Aftre I installed pipewire and pipewire-pulse, the config files were all stored in /usr/share/pipewire/, I had to copy them to /etc/pipewire.
Why not put it in /etc/pipewire in the beginning?
Last edited by laichiaheng (2021-10-15 12:20:28)
Offline
#2 2021-10-15 12:26:43
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,300
Re: Why not put all the PipeWire config files to /etc/pipewire?
It's a common convention that configuration provided by the distributor/the packages are shipped in /usr/share and which then can be adjusted as necessary by copying them into /etc/pipewire by the system administrator (i.e. you )
Offline
#3 2021-10-15 14:05:02
- Trilby
- Inspector Parrot
- Registered: 2011-11-29
- Posts: 30,497
- Website
Re: Why not put all the PipeWire config files to /etc/pipewire?
If a config file is likely to be often used without any adjustment, then packaging it in /etc can make sense. But if what is distributed is just a template or example, then putting it in /etc could be problematic and /usr/share/ is much better. Further, templates in /usr/share can be moved either to the system-wide /etc location or to the user-specific config directories (e.g., under XFG_CONFIG_HOME or ~/.config/).
If configs are packaged in /etc then they'd also need to be listed as backup files, and users would then have to handle the pacnew files on every update. If most users are likely to adjust the config at all or in any way, and the default upstream config is not expected to change that often, then packaging in /usr/share is a no-brainer as it requires one manual intervention on the initial install, then from then on it just works. Packaging under these conditions for /etc would still require a quick edit after the first install, but then a manual intervention after every single update to deal with the pacnew which one would generally just delete anyways (so if it's going to just be deleted most times, why install it there in the first place).
Last edited by Trilby (2021-10-15 14:09:40)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
#4 2021-10-15 19:09:18
- Maniaxx
- Member
- Registered: 2014-05-14
- Posts: 761
Re: Why not put all the PipeWire config files to /etc/pipewire?
Just to make sure. Pipewire doesn't need the configuration files in /etc. This is just an optional step. It works completely fine without them.
sys2064
Offline
#5 2021-10-15 19:53:46
- ugjka
- Member
- From: Latvia
- Registered: 2014-04-01
- Posts: 1,957
- Website
Re: Why not put all the PipeWire config files to /etc/pipewire?
The proper location is $HOME/.config/pipewire/
Offline