From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] Revert "u-boot-custom: Use bitbake variables instead of hardcoded values"
Date: Fri, 23 Nov 2018 19:29:28 +0100 [thread overview]
Message-ID: <9c4bf3e8-5fc3-08f2-862d-544a91cd6174@siemens.com> (raw)
This widely reverts commit 06f80abcb4e80b800e8fdbf512f2a0ddef51d35a.
We can leave the mainline u-boot recipe change, but the one to the core
is wrong. The interface is that custom u-boot recipes provide stable,
PN-independent targets.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/recipes-bsp/u-boot/files/debian/control | 6 +++---
meta/recipes-bsp/u-boot/u-boot-custom.inc | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta/recipes-bsp/u-boot/files/debian/control b/meta/recipes-bsp/u-boot/files/debian/control
index e0ea3eb..6b4c839 100644
--- a/meta/recipes-bsp/u-boot/files/debian/control
+++ b/meta/recipes-bsp/u-boot/files/debian/control
@@ -5,15 +5,15 @@ Standards-Version: 3.9.6
Build-Depends: @BUILD_DEPENDS@
Maintainer: ISAR project <isar-users@googlegroups.com>
-Package: @PN@-@MACHINE@
+Package: u-boot-@MACHINE@
Architecture: @DISTRO_ARCH@
Description: @DESCRIPTION@, bootloader binaries
-Package: @PN@-@MACHINE@-dev
+Package: u-boot-@MACHINE@-dev
Architecture: @DISTRO_ARCH@
Description: @DESCRIPTION@, bootloader libraries
-Package: @PN@-tools
+Package: u-boot-tools
Architecture: linux-any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: @DESCRIPTION@, companion tools
diff --git a/meta/recipes-bsp/u-boot/u-boot-custom.inc b/meta/recipes-bsp/u-boot/u-boot-custom.inc
index 4ec37d0..583cd47 100644
--- a/meta/recipes-bsp/u-boot/u-boot-custom.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-custom.inc
@@ -9,7 +9,7 @@ FILESPATH =. "${LAYERDIR_core}/recipes-bsp/u-boot/files:"
DESCRIPTION ?= "Custom U-Boot"
-PROVIDES += "${PN}-${MACHINE} ${PN}-${MACHINE}-dev ${PN}-tools"
+PROVIDES += "u-boot-${MACHINE} u-boot-tools"
inherit dpkg
--
2.16.4
next reply other threads:[~2018-11-23 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 18:29 Jan Kiszka [this message]
2018-11-23 18:59 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c4bf3e8-5fc3-08f2-862d-544a91cd6174@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox