Hi, Dne 30. 01. 20 v 13:05 Imobach González Sosa napsal(a): [...]
However, it does not contain dependencies information (the "Web and Scripting Module" depends on "Server Applications Module"), so we are not able to display an advice[2].
The question is how much is that add-on dependency information actually needed. I mean if you need a package to install would any extra add-on dependency change your mind? And even when the add-on dependency is known we cannot display the package dependencies. And that is very likely what the user really needs to know because a huge package dependency can change your mind.
I guess we have these options:
1) Do not display this information when working in an unregistered system. When the user clicks "Next", the base system should be registered and, at that point, we will get that info. Then we could display a "Summary" screen informing the user about the dependencies (before registering the modules/extensions).
Um, what if you decide to not continue after registering the base product?
2) Use a "Summary" screen for registered and unregistered systems. See the Alternative Workflow[3] description.
How actually the current workflow works? What if I search for package "foo" and select it to install, then I search for "bar" and select it to install. Finally I search for "baz" but I decide to NOT install it. Can I somehow see all what I have selected so far? If not then a summary dialog would be nice to have anyway.
3) Ask the SCC team to extend the API offering a list of available module/extensions including its dependencies. After all, they already provide a list of base produts through the API[4].
IMHO extending the SCC API is the correct solution for the problem, all other ideas are more or less just workarounds for that missing piece of information.
If you ask me, option 2) should be easy (and quick) to implement but it will change the current workflow. Is it better/worst than the current one? I am not sure (waiting for Ken's feedback).
Depending on the current workflow always displaying the summary might be good anyway.
Option 3) might take more time (we will depend on SCC guys) and I would like to omit option 1).
If 3) is not possible (because of the external dependency) then I would choose 2). Ladislav -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org