| DonHugo | |
| Dec 21 2016, 10:27 PM |
| F8710: 0001-Initial-commit-of-Cronie.patch | |
| Dec 21 2016, 10:27 PM |
Refering to https://dev.solus-project.com/T729
Name: Cronie
Homepage: https://fedorahosted.org/cronie/
Why: Alternative to Dcron, which does not properly work with Back in Time
Is it Open Source: yes
Link to source tarball/zip file: https://fedorahosted.org/releases/c/r/cronie/cronie-1.5.1.tar.gz
Package:
Why is this needed when we have systemd timers? Also, if you're going to file a package request, it needs to be approved first before patches are accepted.
Ups, I'll blame the clock. Thought that because of the .patch file the "Patch Submission" tag is correct....
I agree with you, however I created this task according to your response in https://dev.solus-project.com/T729.
Back in time does not, as far as I can see, support systemd-timers right now (https://github.com/bit-team/backintime/issues/669). Thus a cron daemon is necessary. But Dcron does not work, so this was my "workaround" to get back in time running.
Probably there are also people who prefer cronie over dcron, but the above is the reason I did this.
I don't see why we can't implement a systemd service and timer while we wait for upstream to fix it.