Description of problem: People making decisions for RHEL 8 do not seem to like systemd-timesyncd as they've demonstrated with RHEL 8 by not shipping it, so please split systemd-timesyncd into its own sub-package to ease community interests for RHEL 9 to provide a separate systemd-timesyncd package - quite similar as it has happened for systemd-networkd. Version-Release number of selected component (if applicable): systemd-246.6-3.fc34 Actual results: systemd-timesyncd is part of the main systemd package. Expected results: systemd-timesyncd in its own sub-package.
So... will we be asked to created a separate subpackage for every pointless removal that RHEL does? It's not too much of an issue to create a subpackage, but systemd has ~150 components, and I don't want to end up with another texlive on my hands.
After thinking about this a bit more, I'm inclined to close as WONTFIX. I made an exception for systemd-networkd, because it a) is fairly big, and b) the subpackage was solving an issue that was already extant in coreos. But splitting things out increases complexity and makes the experience worse for the packager and for users. systemd-timesyncd is ~200kb and brings in no additional dependencies.