Hi
On Fri, Nov 13, 2020 at 5:23 PM Matthew Miller wrote:
That reason was _mainly_ to erase the inside Red Hat,
community-around-the-edges distinction. That was a huge success and Fedora
wouldn't be interesting without that. But I think the _technical_ choice was
in retrospect a mistake. There's a reason RHEL 8 switched the _other_ way.
I think for a community distro, having it all in a single repo is technically better as well because part of the problem that was being solved by the merge was not just the community Red Hat delineation but also the issue of build dependencies - core packages couldn't depend on packages from extras and by splitting up repos again you will reintroduce the same problems. So don't do that. What you need is some metadata and the capability for the client tooling to expose that metadata so users can make informed choices on what they are installing and that can be as flexible as you want it to be. apt-listbugs etc does similar things.
Rahul
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
