On 2023-10-16 16:44, Ancor Gonzalez Sosa wrote:
If we want to use patterns as the main concept to allow software customization... What can we do? Organize the patterns better?
I think this is absolutely necessary, yes. Without a comprehensive reworking of the patterns in Tumbleweed I do not see them being useful for Agama
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?
That may be a route to such a reworking. For example, MicroOS requires the equivalent of YaSTs system roles. A YaST system role however is really nothing more than a collection of patterns (which may also alter the installation menus.. but such a concept may make less sense with Agama) A special class of pattern could be a way of implementing this, as patterns can require other 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...
While I agree with the problems and have proposed some suggestions above I just want the record to show I don’t intend to drive a solution to this problem - Aeon doesn’t have any plans to use Agama or more than one pattern at this time, so I’m not deeply impacted by these issues. -- Richard Brown Distributions Architect SUSE Software Solutions Germany GmbH, Frankenstraße 146, D-90461 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Directors/Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich