On Wed, Jun 20, 2018 at 3:49 PM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > > On Wed, Jun 20, 2018 at 03:02:47PM -0400, Josh Boyer wrote: > > > Correct, this is about ensuring that all Fedora installations have > > > access to the modules we build, but there's no change to how > > > they're stored on mirrors, etc. > > Ok. Do we ever foresee the hybrid repository approach happening in Fedora? > > The hybrid approach is "things can be built as modules, but tagged into > the base", right? What problems does this solve vs. allowing modules to No. A hybrid repository is a repository that has both regular RPMs and modules, with repo metadata that describes both. It avoids having a separate repository for each and allows a natural transition from normal RPM to modules without users having to go hunt for their content as it migrates. There are other benefits to it, but it's basically an end user simplification. > be used as dependencies and build deps? That's a different problem. That's something in brew itself, using modules via a different service that talks to MBS. That has utility but needs careful management but it's more centered around developers. josh _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/EQNRJYCZ7EUGZ7CIYZ4TBX2KPFUNJXK4/
