On Mon, Mar 4, 2019 at 11:36 AM Ken Dreyer <ktdreyer@xxxxxxxxxxxx> wrote: > > > > On Fri, Mar 1, 2019, 8:26 AM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: >> >> Not replying to anyone in particular but just a nit for me... >> >> I've been a Fedora packager for probably 10 years now (need to check!) but I *STILL* don't really understand modules other than at a high level (it lets you use dependencies that aren't available in the main repos). I've read through some of the documentation but it's still not clear. I know I would have to crate some kind of module file which I think tools could be developed to mostly automate (spec->module template converter?). >> >> While modularity is more of a Fedora thing I think it's sad that for more standard tools I reference Arch documentation more often than Fedora documentation. Of course there's the, "I could help with that" part and I might, but frankly I can barely keep up with my packages between $DAYJOB, $FAMILY, Fedora, and RPM Fusion. > > > I'm there with you Richard. I don't really get how I can get started building a module outside of the Fedora infrastructure's system (Koji or Copr). > > I'm hoping this gets a lot clearer after modules come in RHEL 8 and we get concrete examples. > This is a known gap. We're having a Modularity hackfest in Boston right now and looking into how we're going to make this simpler and easier. Stay tuned. _______________________________________________ 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
