Those PRs contain much more detailed information and also screenshots:
Author: Stefan Hundhammer [email protected]
The YaST installer is a very powerful, but also very complex tool; it is designed to cover a large variety of Linux installation scenarios. The user is asked a lot of questions in a lot of workflow steps; but in many of these, you can simply click "Next" and rely on the defaults.
In regular intervals, somebody tries to come up with something drastically simpler; an installer that is so dumbed down that it is borderline useless for all but the most trivial cases.
Rough, incomplete, WIP, just to get a discussion going
- Work in a Git branch for the desired released product, e.g. SLE-15-SP42
- Create a pull request from that, get it reviewed and merge it
- Upon merge, a GitHub action will trigger an (internal) Jenkins job:
- Build the package
yast2-pkg-bindings in SLE-15-GA:
https://build.suse.de/request/show/240601
This was declined with:
Please provide fixes for
This is related to the YaST Installer Steps document, but items are rearranged here to make the distinction clear between
- Settings for the installation procedure (installation language, keyboard)
- Installation preparation (storage setup, ???)
- Collecting data for later configuration
See also the simple standard installation screenshots (openSUSE Tumbleweed installation).
Detect
- system architecture
GitHub offers hosting documentation on GitHub Pages. This can be done once for each GitHub user, for each GitHub organization, for each GitHub project.
If the process for building the autodocs is already in place (as is the case for libyui), it is just a matter of generating them, moving them to the right place, and deploying them to the project's GitHub Pages.