-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add bootloader pattern for all roles #44
Conversation
YaST will install all the packages that are resolved from the patterns listed in the control.xml (for a selected role). Internally also have a list of packages that are installed that do not come from any external requirement, for example the kernel or the Grub bootloader. Since some time ago there is a pattern bootloader in the pattern-base package, that can be used to explicitly drive an installation that requires a bootloader. This is an exercise to re-use the same patterns for containers, that will not require a bootloader. This patch makes explicit the requirement of the bootloader pattern.
Related with https://build.opensuse.org/request/show/935234 |
👍 |
Interesting, how bootloader pattern works? It select proper bootloader target based on hardware information and architecture? |
Indeed: https://build.opensuse.org/package/view_file/system:install:head/patterns-base/patterns-base.spec?expand=1 |
❌ Public Jenkins job #44 failed |
YaST will install all the packages that are resolved from the patterns
listed in the control.xml (for a selected role). Internally also have
a list of packages that are installed that do not come from any
external requirement, for example the kernel or the Grub bootloader.
Since some time ago there is a pattern bootloader in the pattern-base
package, that can be used to explicitly drive an installation that
requires a bootloader. This is an exercise to re-use the same
patterns for containers, that will not require a bootloader.
This patch makes explicit the requirement of the bootloader pattern.