[Bug 2350109] Review Request: systemd-cron - systemd-generator implementing cronie and anacron

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=2350109



--- Comment #56 from Pramod V U <pramodvu1502@xxxxxxxxx> ---
"Alternatives" mechanism would be too complicated, considering that
crond.service and cron.target are 2 different units...

Yes, systemd does have a `Conflicts=` though, which could be used in
cron.target here...
Should I add a `Conflicts=crond.service` to cron.target?

> To be clear to you, I won't accept this review with the current hacks for cronie. I really dislike any hard-couplings with cronie (what if cronie gets renamed, that would require changes in this package).

I agree, but the "solution(s)" is/are not that simple... will need a bit of
time...

Is it possible to amend cronie.spec to `Provides: cron` and make all packages
having `Requires: cronie` to instead depend on `cron`?
AND `Provides: cron` in this package too.

Yes, alternatives mechanism is ultimately needed, for the "crontabs" binary.
But if it *is* possible for the crond.service and cron.target units, and it's
not too complicated, it might be fine.

So I propose the following solutions:
- Alternatives mechanism for %{_bindir}/crontab binary...
- systemd.unit Conflicts=crond.service
- Alternatives mechanism for crond.service <-> cron.target if possible...
- If really needed, every cron daemon `Provides: cron` and every dependant
`Requires: cron`... If really needed.
- What else? A better solution?


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2350109

Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202350109%23c56

-- 
_______________________________________________
package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite Conditions]     [KDE Users]

  Powered by Linux