public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [RFC PATCH 1/1] meta/dpkg-raw: support for special debian package dependencies
Date: Wed, 13 Dec 2017 17:07:10 +0100	[thread overview]
Message-ID: <20171213160710.3610-2-claudius.heine.ext@siemens.com> (raw)
In-Reply-To: <20171213160710.3610-1-claudius.heine.ext@siemens.com>

From: Claudius Heine <ch@denx.de>

Now special debian dependencies can be specified in the recipe like
this:

    DEBIAN_DEPENDS = "'libc (>= 2.16)' 'tar | bsdtar' systemd"

and the package contains this 'Depends' entry:

    Depends: libc (>= 2.16), tar | bsdtar, systemd

Signed-off-by: Claudius Heine <ch@denx.de>
---
 meta/classes/dpkg-raw.bbclass | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/classes/dpkg-raw.bbclass b/meta/classes/dpkg-raw.bbclass
index 1435e10..42a33e0 100644
--- a/meta/classes/dpkg-raw.bbclass
+++ b/meta/classes/dpkg-raw.bbclass
@@ -31,9 +31,9 @@ do_deb_package_prepare() {
 	__EOF__
 	if [ ${DEBIAN_DEPENDS} != "" ]
 	then
+		DEBIAN_DEPS="$(for i in ${DEBIAN_DEPENDS};do echo $i,;done|tr '\n' ' '|sed 's/, *$//')"
 		echo -n Depends: >> ${D}/DEBIAN/control
-		echo ${DEBIAN_DEPENDS} | tr '[:blank:]' ',' >> \
-			${D}/DEBIAN/control
+		echo " ${DEBIAN_DEPS}" >> ${D}/DEBIAN/control
 	fi
 	for t in pre post
 	do
-- 
2.15.1


  reply	other threads:[~2017-12-13 16:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 16:07 [RFC PATCH 0/1] Special debian depends entries claudius.heine.ext
2017-12-13 16:07 ` claudius.heine.ext [this message]
2017-12-14 13:42 ` Henning Schild
2017-12-14 14:12   ` Claudius Heine
2017-12-14 14:36     ` Henning Schild
2017-12-14 14:52       ` Claudius Heine
2017-12-14 16:20         ` Henning Schild
2017-12-14 17:02           ` Claudius Heine
2017-12-14 17:31             ` Henning Schild
2017-12-15  8:24               ` Claudius Heine

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=20171213160710.3610-2-claudius.heine.ext@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=ch@denx.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