public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH 4/4] u-boot: Remove BUILD_DEPENDS backward compatibility
Date: Thu, 14 Mar 2024 11:41:14 +0200	[thread overview]
Message-ID: <20240314094114.3867735-5-amikan@ilbers.de> (raw)
In-Reply-To: <20240314094114.3867735-1-amikan@ilbers.de>

BUILD_DEPENDS usage in u-boot-custom.inc has been deprecated since v0.8
and now we can remove backward compatibility and warning message.
DEBIAN_BUILD_DEPENDS should be used instead.

Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
 meta/recipes-bsp/u-boot/u-boot-custom.inc | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/meta/recipes-bsp/u-boot/u-boot-custom.inc b/meta/recipes-bsp/u-boot/u-boot-custom.inc
index 25f0e1ef..8aea773d 100644
--- a/meta/recipes-bsp/u-boot/u-boot-custom.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-custom.inc
@@ -18,12 +18,6 @@ inherit dpkg
 
 SRC_URI += "file://debian/"
 
-python() {
-    if d.getVar('BUILD_DEPENDS'):
-        bb.warn("u-boot-custom: Deprecated use of BUILD_DEPENDS, please switch to DEBIAN_BUILD_DEPENDS")
-        d.setVar('DEBIAN_BUILD_DEPENDS', d.getVar('BUILD_DEPENDS'))
-}
-
 DEBIAN_BUILD_DEPENDS ?= "bc, bison, flex, device-tree-compiler, git"
 
 TEMPLATE_FILES = "debian/control.tmpl debian/rules.tmpl"
-- 
2.34.1


  parent reply	other threads:[~2024-03-14  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  9:41 [PATCH 0/4] Remove deprecated variables and classes Anton Mikanovich
2024-03-14  9:41 ` [PATCH 1/4] rpi: Remove deprecated rpi-sdimg.bbclass Anton Mikanovich
2024-03-14  9:41 ` [PATCH 2/4] image: Remove IMAGE_TRANSIENT_PACKAGES deprecation warning Anton Mikanovich
2024-03-14  9:41 ` [PATCH 3/4] image: Remove backward compatibility with IMAGE_TYPE Anton Mikanovich
2024-03-14  9:41 ` Anton Mikanovich [this message]
2024-03-22  8:17 ` [PATCH 0/4] Remove deprecated variables and classes Uladzimir Bely

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=20240314094114.3867735-5-amikan@ilbers.de \
    --to=amikan@ilbers.de \
    --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