On Tue, 28 Mar 2017, Thorsten Kukuk wrote:
On Tue, Mar 28, Brüns, Stefan wrote:
Yes. For example /etc/cron.{d,daily,hourly,monthly,weekly}, which are all owned by filesystem.
They should be owned by cron, so that they are not there if there is no cron daemon and, RPMs shipping cron files, require cron so that they can be executed ...
Or rather RPMs that have cron files should ship configuration (cron files) separately from their main feature and the cron files package should supplement cron? I've never understood why we so closely tie default configuration with package requirements so you can't install some packages without dependencies you are never going to use (because you choose a different leaner configuration). IMHO dependencies tied to (default) configuration should come with a flavor package providing the (default) configuration. Pie in the sky... Richard.
Thorsten
--
Richard Biener