This change nearly reverts the condition for cron job support, so please explain in more detail why you think it needs to be this way.

My goal is to submit this package to Factory, and I can't do that if the package cron is recommended.

With this modification, we still provide the cron example without recommending the cron package. However, if you believe it is better to recommend the cron package for 15 SPX, I could just select Tumbleweed.

What do you think? Also, @lrupp what is your opinion?

Lars Vogdt (lrupp) - 9 months ago

target maintainer

Getting rid of cron if there is a working systemd-timer available is IMHO the right approach. Still providing the cron file as example might help people, who either migrate or need an example for other reasons.

So: all ok from my pov.

---

Reinhard Max (rmax) - 9 months ago

target maintainer

I didn't mean to question the deprecation of cron, I was just wondering that the submission reversed the direction of the comparison in the condition for enabling or disabling cron. But at a closer look, it appears that the old version was wrong, not the change.

In any case, I realized that the changelog entry is misleading and incorrect.