On Wed, Oct 09, 2019 at 04:46:52PM -0400, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/Modules_In_Non-Modular_Buildroot > > Enable module default streams in the buildroot repository for modular > and non-modular RPMs. > > == Summary == > This Change (colloquially referred to as "Ursa Prime") enables the > Koji build-system to include the RPM artifacts provided by module > default streams in the buildroot when building non-modular (or > "traditional") RPMs. > > == Owner == > * Name: [[User:Sgallagh| Stephen Gallagher]] > * Email: sgall...@redhat.com > * Responsible WG: Modularity WG
Thanks for writing this up Stephen, I fully support this. For some people here it is clear they don't want to develop modules and that will always be fine. Others see a benefit (whether small or large) from developing as modules, and that should also be fine and I want Fedora to allow that. Allowing modules in buildroots prevents the conflict between packagers who make different choices (e.g. non-modular Eclipse can't use module-only Maven) so seems like a good compromise. I find myself a bit reluctant to write this mail because the language others are using in this thread is fairly ugly for a technical discussion in an open source project - about "forcing" people to develop packages in a certain way, "teaching them a lesson" etc. Please calm it down & have some respect for technical decisions of other developers. Regards, Joe _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
