From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [RFC 4/5] hello-isar: Remove duplicated dependency
Date: Fri, 25 Feb 2022 10:40:39 +0300 [thread overview]
Message-ID: <20220225074040.20975-5-amikan@ilbers.de> (raw)
In-Reply-To: <20220225074040.20975-1-amikan@ilbers.de>
Remove build dependency already mentioned in debian/control.
We will parse all the deps automatically without need in manual
dependency duplication.
Warning! Normal Isar build will fail after that!
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
meta-isar/recipes-app/hello-isar/hello-isar.bb | 4 ----
1 file changed, 4 deletions(-)
diff --git a/meta-isar/recipes-app/hello-isar/hello-isar.bb b/meta-isar/recipes-app/hello-isar/hello-isar.bb
index 8c3ba8b..20794c2 100644
--- a/meta-isar/recipes-app/hello-isar/hello-isar.bb
+++ b/meta-isar/recipes-app/hello-isar/hello-isar.bb
@@ -10,10 +10,6 @@ LIC_FILES_CHKSUM = "file://${LAYERDIR_core}/licenses/COPYING.GPLv2;md5=751419260
PV = "0.3-a18c14c"
-# NOTE: the following line duplicates the content in 'debian/control', but
-# for now it's the only way to correctly build bitbake pipeline.
-DEPENDS += "libhello"
-
SRC_URI = " \
git://github.com/ilbers/hello.git;protocol=https;destsuffix=${P} \
file://subdir/0001-Add-some-help.patch \
--
2.25.1
next prev parent reply other threads:[~2022-02-25 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 7:40 [RFC 0/5] Debian dependencies investigation Anton Mikanovich
2022-02-25 7:40 ` [RFC 1/5] dpkg-base: Cover do_apt_unpack task by lock Anton Mikanovich
2022-02-25 17:30 ` Jan Kiszka
2022-02-25 7:40 ` [RFC 2/5] meta: Implement two stage build Anton Mikanovich
2022-02-25 7:40 ` [RFC 3/5] libhello: Declare provided packages Anton Mikanovich
2022-02-25 7:40 ` Anton Mikanovich [this message]
2022-02-25 7:40 ` [RFC 5/5] isar: Add external builder Anton Mikanovich
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=20220225074040.20975-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