On Thursday, October 10, 2019 5:59:16 PM CEST Miro Hrončok wrote: > On 10. 10. 19 17:46, Igor Gnatenko wrote: > > On Thu, Oct 10, 2019 at 12:52 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > >> > >> On 09. 10. 19 22:46, 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: sgallagh@xxxxxxxxxx > >>> * Responsible WG: Modularity WG > >>> > >>> == Detailed Description == > >>> As a major part of the Modularity design, we have a concept of default > >>> module streams. These streams are built as modules, but the RPM > >>> artifacts they deliver are intended to be used just like non-modular > >>> RPMS. The aspirational goal is that a user of the system who never > >>> executes a module-specific command (such as `dnf module install > >>> nodejs:8`) should experience no meaningful changes in behavior from > >>> how they would interact with a completely non-modular system. In > >>> practice, this may mean that the informational output of package > >>> managers may indicate that modules are being enabled and used, but a > >>> user that does not have a specific reason to interact with the > >>> selection of a module stream should have that managed on their behalf. > >> > >> If this is the goal of default modular streams, wouldn't it be in fact much > >> easier to keep the default versions as urisne packages? > > > > That means, you have 2 different workflows: for default version and > > for an additional one. > > When branching happens, instead of just updating one file which points > > to the new default, you would have to create new stream, retire the > > one which is about to become default and update package in > > non-modular. > > > Yes. It puts additional (arguably fairly trivial) work for the modular > maintainers. Other than that, it makes lives of every other maiantainar, of the > dnf maintainers and of Fedora users easier. > > I call it a good deal. +1, that's pattern we decided to do in case of PostgreSQL. Pavel _______________________________________________ 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
