On Fri, Nov 13, 2020 at 05:46:46PM -0500, Rahul Sundaram wrote:
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
But that's policy as well. It would be reasonable to have a different policy, like "build and soft dependencies are okay from base -> secondary, but not hard runtime requirements".
... but anyway:
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.
Yeah, a metadata-based approach works for me as well.