Re: Summary/Minutes from today's FESCo Meeting (2020-11-11)

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

 



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.


-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux