Overview
We neeed BuildRequires because we run some unit tests against that package during build.
For Requires it's a question, I do not think it is strictly needed. It depends whether the final product actually uses that NTP dialog or not.
If it does than the Requires should be added to the respective product skelcd package, like https://github.com/yast/skelcd-control-openSUSE/blob/392dba66dc012fe2491cb27b9d8430335e9bc093/package/skelcd-control-openSUSE.spec#L65
Omitting the Requires allows having a smaller inst-sys (without yast2-ntp-client) if it is not used during installation.
Yes, it makes sense - it just looked suspicious that all other yast2- dependencies were Requires and not only BuildRequires.
We seem to end up with a cycle here:
Package yast2-installation appears in cycle yast2-installation/yast2-ntp-client Package yast2-ntp-client appears in cycle yast2-installation/yast2-ntp-client
Request History
yast-team created request
submit new version 4.2.2
licensedigger accepted review
ok
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
dimstar_suse set openSUSE:Factory:Staging:J as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:J"
dimstar_suse accepted review
Picked openSUSE:Factory:Staging:J
dimstar accepted review
dimstar_suse accepted review
ready to accept
dimstar_suse approved review
ready to accept
dimstar_suse accepted request
Accept to openSUSE:Factory