On Tue, Nov 12, 2019 at 3:29 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > On Tue, Nov 12, 2019 at 3:20 PM Stephen Gallagher <sgallagh@xxxxxxxxxx> wrote: > > > > On Tue, Nov 12, 2019 at 11:10 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > > > On Tue, Nov 12, 2019 at 11:03 AM Aleksandra Fedorova <alpha@xxxxxxxxxxxx> wrote: > > > > > > > > Again, no one forces you or any other packager to use modularity > > > > tooling right now. > > > > > > > > > > This is not true. Once content is modularized, things that were able > > > to depend on it in the normal form can no longer do so unless they too > > > modularize. > > > > This is true *currently*, but as I've been saying for months now: this > > is only true because we've not been allowed to land Ursa Prime (and, > > before that, Ursa Major) to allow us to have modules in the buildroot. > > > > That *finally* started to change with FESCo's decision yesterday. They > > gave us permission to put two reasonably-contained modules into the > > available buildroot to prove it out. > > > > I am watching that experiment carefully. I'm doing something similar > for my own work as an experiment into pulling in modular content into > my build environments... > > > > This is an important consequence that I think people > > > championing for modularity keep forgetting. Everything from how the > > > build system works to how DNF implements modularity makes it so that > > > modular and non-modular content do not have an even footing. If they > > > did, I think we'd have less problems. > > > > I think "even footing" is a poor choice of words, because it implies > > that one is "higher" than the other. It's true that things are built > > and managed *differently*. We've been trying to close that gap as much > > as possible. > > Technically, one is "higher" than the other. Modular content > automatically disables the non-modular counterparts. You don't have > the ability to select to install and follow content fron the > non-modular source instead of the modular one, especially with > fedora-modular enabled by default. > > If there is a path for me to freely switch back and forth between > equivalent modular and non-modular variants, I'd definitely be > happier, personally. `dnf module disable foo` *should* be able to do this. If that doesn't work in all cases, there are bugs. I just tested myself that I could do `dnf module disable meson && dnf downgrade meson` and I got the non-modular package on my F31 system. (If the non-modular one had been a higher ENVR, I would have been able to do `dnf update meson`.) _______________________________________________ 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
