-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat(wic-tools): add efibootguard dependency #21
base: master
Are you sure you want to change the base?
Conversation
To make it a bit more Yocto compatible (a layer should not change something unconditionally) and less ARCH specific I would propose:
|
Similar to other EFI_PROVIDER possibilities which are added already in poky
8b7c4df
to
c3f9efa
Compare
The old 0.11 release supported x86 (32 and 64 bit) and arm64. 0.12 enabled also 32-bit ARM. RISC-V is on the horizon, just not yet for the next release. |
I'm kind of undecided if we should use append by architecture or just append when we use it. |
I see your point. In poky there is (https://git.yoctoproject.org/poky/tree/meta/recipes-core/meta/wic-tools.bb#n12)
The more different bootloaders have to be supported, the less sense the implementation in poky makes. Who wants to build all bootloaders for all machines? Usually one bootloader per machine is enough. What about changing poky to:
For meta-efibootguard we could then do:
Transition from current state to proposed state:
|
Similar to other EFI_PROVIDER possibilities which are added already in poky
I'm actually not sure which architectures are supported by efibootguard, so we may need to add more archs