m (moved Packaging talk:Guidelines:Systemd to Packaging talk:Systemd) |
(.service/.timer files as %config) |
||
Line 5: | Line 5: | ||
There should be mentioned rule about files in /var/run and /var/lock. Regular files in /var/run and /var/lock directories should be packaged as %ghost. For directories use tmpfiles.d(5) mechanism without %ghost. --plautrba | There should be mentioned rule about files in /var/run and /var/lock. Regular files in /var/run and /var/lock directories should be packaged as %ghost. For directories use tmpfiles.d(5) mechanism without %ghost. --plautrba | ||
"''Systemd unit .service files must not be marked as %config files.''" - I disagree, those are files commonly customized ('''.service''' ones for example nice/idle daemon priority). It does not mention '''.timer''' files, those also should be %config so that their modifications do not get lost. |
Revision as of 21:47, 18 April 2020
What I am missing is a explicit guideline on whether one should continue packaging init scripts and unit files or drop the init scripts in Rawhide
-- Rahul Sundaram
There should be mentioned rule about files in /var/run and /var/lock. Regular files in /var/run and /var/lock directories should be packaged as %ghost. For directories use tmpfiles.d(5) mechanism without %ghost. --plautrba
"Systemd unit .service files must not be marked as %config files." - I disagree, those are files commonly customized (.service ones for example nice/idle daemon priority). It does not mention .timer files, those also should be %config so that their modifications do not get lost.