On Tue, 2023-10-24 at 14:57 +0200, Ancor Gonzalez Sosa wrote:
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
How would you translate https://openqa.opensuse.org/tests/3671973#step/system_role/3 into this? Assuming that those 'roles' are to be expressed as different patterns, we'd need to expose them. exposing them means the installer sees all the installer relevant patterns from the repo. Cheers, Dominique