From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] debianize: Allow defining additional build dependencies
Date: Fri, 3 Apr 2020 18:29:15 +0200 [thread overview]
Message-ID: <5f45f046-2c2a-96c6-aca6-e43d7f42a148@siemens.com> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
This avoids the not very uncommon sed patterns after deb_debianize,
injecting additional build dependencies.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
RECIPE-API-CHANGELOG.md | 5 +++++
meta/classes/debianize.bbclass | 3 ++-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index fc416a4f..a444e32a 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -236,3 +236,8 @@ downloads from previous builds for the cache.
DTB_FILES now allows to specify multiple DTBs that should be deployed for
consumption by imaging classes.
+
+### Add DEBIAN_BUILD_DEPENDS as deb_debianize parameter
+
+Additional build dependencies of auto-debianized packages can now be defined
+by setting DEBIAN_BUILD_DEPENDS.
diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass
index f07a432c..da43a4e2 100644
--- a/meta/classes/debianize.bbclass
+++ b/meta/classes/debianize.bbclass
@@ -5,6 +5,7 @@
CHANGELOG_V ?= "${PV}"
DPKG_ARCH ??= "any"
+DEBIAN_BUILD_DEPENDS ?= ""
DEBIAN_DEPENDS ?= ""
DESCRIPTION ?= "must not be empty"
MAINTAINER ?= "Unknown maintainer <unknown@example.com>"
@@ -49,7 +50,7 @@ Section: misc
Priority: optional
Standards-Version: 3.9.6
Maintainer: ${MAINTAINER}
-Build-Depends: debhelper (>= ${compat})
+Build-Depends: debhelper (>= ${compat}), ${DEBIAN_BUILD_DEPENDS}
Package: ${PN}
Architecture: ${DPKG_ARCH}
--
2.16.4
next reply other threads:[~2020-04-03 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 16:29 Jan Kiszka [this message]
2020-04-17 16:32 ` Baurzhan Ismagulov
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=5f45f046-2c2a-96c6-aca6-e43d7f42a148@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