Lars Vogdt wrote:
Hi Lukas
Ideas and comments are welcome! ;)
I'm thinking about an easy solution => What about creating "yast2-<module>-installme" packages?
Those "installme" packages: 1) have a "dimmed" icon (and desktop file) for the section where the normal module will be installed 2) have a special desktop file which lists them in your "Not Yet Installed" section
The normal "yast2-<module>" packages will provide/obsolete their corresponding "yast2-<module>-installme" packages.
The "installme" packages should be very small as they just have a desktop-file and an icon-file and should be recommended by one your new yast2-not-yet-installed module (or another yast2-) package which is recommended in the yast2 pattern.
As result, you should get the best of both ideas - dimmed icons and an extra section for non-installed modules and the possibility for "experts" to skip the whole stuff.
Idea yast2-<module>-installme packages sounds good. 1.) Solves the problem with different icons (dimming could be done automagically while building the package / but it would ignore different YaST themes and we still haven't decided how we could include an icon in YaST package). 2.) The same way I did it I guess (but this would be "per package" instead of "all in one"). Honestly, I'm not sure how the provides/obsoletes works in libzypp by I'd assume new package (e.g., yast2-dns-server) just silently replaces the 'old' one (e.g., yast2-dns-server-installme). Could this work if both packages were on the same media conflicting with each other? Anyway, if it worked, we wouldn't have to change any of the current YaST Control Centers (Qt, GTK, ncurses). This idea sounds like a more generic solution and a package could but needn't provide its "-installme" subpackage but on the other hand creating such a product with all the dependencies would be more complicated. BTW: Do we really want to have 'approximately' (rpm -qa | grep yast2 | wc -l) -> 117 new packages? L.