Re: Fedora 32 System-Wide Change proposal: Modules in Non-Modular Buildroot

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

 



On Wed, Oct 16, 2019 at 01:28:37PM -0400, Stephen Gallagher wrote:
> 1) This will be solved by the new Koji/MBS feature that we've
> codenamed "Ursa Prime" (as a replacement for the original "Ursa Major"
> tool that was built for RHEL 8). Unlike its predecessor, it requires
> no additional daemon service running to handle things. We will create
> a buildroot compose for each release that is created from the set of
> packages available from all of the default streams and both Koji (in
> infra) and mock (on packager systems) will be able to consume this.
> Koji will behave the same as mock, where it will rely on libdnf's
> default module stream handling to populate the buildroot, so we won't
> have to worry about disparities between the local and infrastructure
> packager experiences.

How would this act in the case where a default stream depends on a
non-default stream?

(And how would restricting default streams to only be able to depend on
default streams change things?)


-- 
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