We need to talk. ;-) As you may know, the YaST Team is developing an alternative installer called Agama (formerly D-Installer). https://github.com/openSUSE/agama We want the workflow in Agama to be simpler than with YaST. Even without any selection of packages to install. But quite some people expressed their desire of being able to customize the software selection while installing the operating system itself. Since we don't want to bring back complex and specific concepts like the installation roles, we decided to expose the current list of patterns so the users can decide which ones to install... knowing that would expose some organizational problems we have with patterns. Take a look at https://yast.opensuse.org/assets/images/patterns-demo.gif That's a first implementation that shows we have WAY too many patterns that are WAY too arbitrarily organized. If we want to use patterns as the main concept to allow software customization... What can we do? Organize the patterns better? Introduce some kind of flag to distinguish the patterns that make sense to offer during installation? Fix something in the way we categorize the patterns? We feel this is not an UI problem, but an structural one. We are looking forward for realistic suggestions. Meanwhile, you can play with the current list by downloading the staging version of Agama. Ie. any image called agama-live-xxx-openSUSE-yyy.iso from https://download.opensuse.org/repositories/systemsmanagement:/Agama:/Staging... Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions