FS#59336 - [pipewire] enable the socket in the package instead of the .install script
Attached to Project:
Arch Linux
Opened by nl6720 (nl6720) - Saturday, 14 July 2018, 12:18 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 21 August 2018, 14:38 GMT
Opened by nl6720 (nl6720) - Saturday, 14 July 2018, 12:18 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 21 August 2018, 14:38 GMT
|
Details
Description:
All the .install script does is enable the user socket. This creates an untracked file "/etc/systemd/user/sockets.target.wants/pipewire.socket". It might be better to just package a symlink to enable the socket. Additional info: * package version(s) * config and/or log files etc. pipewire 0.1.9-3 Steps to reproduce: pacman -Qo /etc/systemd/user/sockets.target.wants/pipewire.socket |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Tuesday, 21 August 2018, 14:38 GMT
Reason for closing: Not a bug
Additional comments about closing: untracked files in /etc are not a bad thing, and in this case they're a feature that prevents manually-disabled sockets from being surprisingly re-enabled on upgrades and breaking pacman -Qkk in the meantime.
Tuesday, 21 August 2018, 14:38 GMT
Reason for closing: Not a bug
Additional comments about closing: untracked files in /etc are not a bad thing, and in this case they're a feature that prevents manually-disabled sockets from being surprisingly re-enabled on upgrades and breaking pacman -Qkk in the meantime.