On Tue, Aug 1, 2017 at 11:47 PM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > On Mon, Jul 31, 2017 at 10:59:58AM -0400, Matthew Miller wrote: >> The thing that jumps out immediately is that respondents _really_ >> prefer the "dnf module install httpd" syntax — 73% love or like that, >> while 7% dislike or hate it. 21% love or like "dnf install httpd" for installing >> modules, while 46% dislike or hate it. And a full half of that dislike >> is hate, or in other words more people completely hate it than like or >> love it _combined_. The "dnf install @httpd" syntax gets just a little >> bit less hate, but also less love. > > I talked to Langdon, who is a strong advocate of the "bare" `dnf > install httpd` syntax. > > His argument is that modules should be seen as if they are > metapackages¹, and that it would be an odd extra step to have to > effectively first enable the ability to install packages and _then_ > install them. I'll let Langdon make his own argument, but basically > akin to shipping Fedora split in different repos, some of them > disabled. That's because with the other options, if you install Modular > Fedora and don't have an enabled module containing the package you ask > for, you get "that doesn't exist".² > > This did not convince me, exactly — but it did sway me in favor of the > `dnf install @httpd` syntax. That's because I think these are really > more like Super Comps Groups (with more and better metadata and > multi-stream powers!) than they are like virtual packages, and I still > think the bare syntax is confusing because behavior will be different > based on something you might not know before you run the command. And > we already _have_ the @whatever syntax for comps groups. How does it distinguish between comps groups and modules, how does it resolve conflcits between the two? I think a designator makes sense but I don't think that should be @ Peter _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
