On 11/2/23 00:07, Björn Bidar wrote:
Ancor Gonzalez Sosa <ancor@suse.de> writes:
[...]
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
That sounds very good, it would also make it much easier for OEM's or organizations to modify the installer this way.
I found it difficult to configure such options such as repository in the current yast based installer.
I'm curious to know why. The Agama philosophy in that regard is quite similar to the YaST one (as a matter of fact, it's based on the very same concepts). Of course, Agama offers fewer options and uses Yaml instead of XML. But I'm curious to know what other factors you think make YaST hard to configure, just to avoid repeating errors in Agama. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions