On 10/24/23 14:14, Dominique Leuenberger wrote:
On Tue, 2023-10-24 at 13:23 +0200, Ancor Gonzalez Sosa wrote:
Well, if we get a new flag for "installer-related" patterns I actually don't care about the visible flag and its status. ;-)
Thge most tricky part about that is 'multi-product repositories' (e.g openSUSE:Factory) - currently we produce multiple product media (MicroOS, Tumbleweed) with their own respective roles - but software selection wise, they all have access to the 'one big repo'.
If Agama goes the route of * Selecting the product, which decides RO/RW * Selecting patterns to pick the install 'role'
Then MicroOS will offer exactly the same as Tumbleweed (the same underlying repositories, thus also the same patterns)
Yes and no. If I correctly understood what the status quo is. That could easily be translated to something similar to this two product configurations: Agama configuration for MicroOS =============================== software: repository: - http://the.same.repos/oss - http://the.same.repos/update mandatory_patterns: - microos_base patterns_configurable_by_user: false storage: transactional: true transactional_configurable_by_user: false Agama configuration for Tumbleweed ================================== software: repository: - http://the.same.repos/oss - http://the.same.repos/update mandatory_patterns: - enhanced_base optional_patterns: # This would make Gnome the default desktop. Don't panic, # just as example. - installation_gnome patterns_configurable_by_user: true storage: transactional: false transactional_configurable_by_user: true The syntax in those examples is highly modified for easier understanding, but they actually reflect quite closely the kind of things that are configured by product at https://github.com/openSUSE/agama/blob/master/service/etc/agama.yaml Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions