On 2018-08-31 14:28, Bach, Pascal (BT CPS R&D ZG FW CCP) wrote:
-----Original Message-----
From: Jan Kiszka <[email protected]>
Sent: Freitag, 31. August 2018 14:16
To: Bach, Pascal (BT CPS R&D ZG FW CCP) <[email protected]>;
[email protected]
Subject: Re: [meta-efibootguard][PATCH] Rename base package to
efibootguard
On 2018-08-30 16:02, [ext] Pascal Bach wrote:
When setting the EFI_PROVIDER variable two things are expected:
1. A package with the name ${EFI_PROVIDER} exists that is included in
packagegroup-core-boot 2. A bbclass with the name ${EFI_PROVIDER}
exists
With the current layer there is a class called efibootguard but the
package is called efibootguard-efi. These do not match.
This renames the base package to efibootguard to match the class name.
This is also in line with how systemd-boot and grub-efi work.
Signed-off-by: Pascal Bach <[email protected]>
---
recipes-bsp/efibootguard/efibootguard.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-bsp/efibootguard/efibootguard.bb
b/recipes-bsp/efibootguard/efibootguard.bb
index 3449fda..7d1081e 100644
--- a/recipes-bsp/efibootguard/efibootguard.bb
+++ b/recipes-bsp/efibootguard/efibootguard.bb
@@ -28,7 +28,7 @@ PACKAGES = "${PN}-tools-dbg \
${PN}-tools-staticdev \
${PN}-tools-dev \
${PN}-tools \
- ${PN}-efi"
+ ${PN}"
EXTRA_OECONF = "--with-gnuefi-sys-dir=${STAGING_DIR_HOST} \
--with-gnuefi-include-dir=${STAGING_INCDIR}/efi \ @@
-38,7 +38,7 @@ FILES_${PN}-tools = "${bindir}"
FILES_${PN}-tools-dbg = "/usr/src/debug ${bindir}/.debug /usr/lib/debug"
FILES_${PN}-tools-staticdev = "${libdir}/lib*.a"
FILES_${PN}-tools-dev = "${includedir}/${BPN}"
-FILES_${PN}-efi = "${libdir}/${BPN}"
+FILES_${PN} = "${libdir}/${BPN}"
do_deploy () {
install ${B}/efibootguard*.efi ${DEPLOYDIR}
Thanks, applied to next, targeting master, thus rocko+. If you think this
should go into other branches as well, let us know.
The patch is a result of me trying to get this layer working with current OE
master (sumo+).
I have some more patches in the pipeline but they require a new release of
efibootguard that includes the GCC 8 fixes.
We originally had at least that recovery mode on the feature list for a
next release. That got delayed now, so it might be a good point for an
earlier release if it helps.
Andreas, what do you think?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
--
You received this message because you are subscribed to the Google Groups "EFI Boot
Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/efibootguard-dev/35e6fd9e-3049-4e5e-01f0-44f7db7a8ef5%40siemens.com.
For more options, visit https://groups.google.com/d/optout.
