Conflicts between cron implementations

[r-ricci]

I noticed there are some conflicts between some of the cron implementations in Void repositories. They are related to the default crontables shipped with the packages. Currently, I've taken into account only cronie and dcron, but similar issues probably affect other combinations of cron too.

E.g.: dcron ships /var/spool/cron/root, which is used to run jobs in /etc/cron.{hourly,daily,weekly,monthly}. If another cron daemon is enabled on the system and dcron is installed but not enabled, this file shipped by dcron is read by the enabled daemon. And if this uses some other mechanism (e.g. cronie relies on anacron) to run the jobs in the above directories, the jobs would run twice. Also, cronie ships /etc/cron.hourly/0anacron, which would be used by dcron (or another cron), if enabled. But anacron would run the same jobs already ran by the root's crontab of dcron.

I'm not sure what's the best way to fix this kind of issues. These packages not only couldn't be used at the same time (of course), but they can't even coexist on the same filesystem, if one of them is enabled. So the most robust fix would be to make the various cron packages conflict on each other. But I think alternatives have been set up because we want to avoid this.

[classabbyamp]

just move /var/spool/cron/root elsewhere and add it to dcron's cron alternatives group? and similarly for other files in other crons

[github-actions[bot]]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.