On Thu, Aug 24, 2017 at 7:44 AM, Stephen Gallagher <sgallagh@xxxxxxxxxx> wrote: > > > On Thu, Aug 24, 2017 at 3:02 AM Marius Vollmer <marius.vollmer@xxxxxxxxxx> > wrote: >> >> My understanding from playing with Boltron is that "dnf install foo" >> treats "foo" as a module name. "dnf install" can not install packages >> anymore. So naively I assume that PackageKit will transparently start >> installing modules. (I think PK uses libdnf, and I think I read >> somewhere that libdnf doesn't do anything with modules yet, so...) > > > This is not true. The modularity-aware DNF will first check to see if a > module matching the requested name exists and will install that. If it > doesn't, it will fall back to packages. > > That being said, the implementation is still under debate. I'm personally of > the opinion that this is the correct behavior (since it requires no > adaptation for users), but there are some people who believe that it should > be explicit with `dnf module install` instead of `dnf install`. > This is a stupid idea because it introduces "magic" into picking the type of thing installed. It also goes against how we typically do this. You either have a modifier that indicates you want to install a module, or you have a module subcommand that has install/remove/upgrade subcommands. I really hope the DNF team doesn't go through with that idea, as it's super-Fedora specific and not really helpful for people who may want to choose to ignore Modularity stuff (since it doesn't apply to them), and other distributions now use DNF (Mageia, Yocto, etc.) that really don't want this. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
