public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] dpkg-base: Expect *.deb relative to S not WORKDIR
Date: Mon, 14 May 2018 17:34:42 +0200	[thread overview]
Message-ID: <20180514153442.1409-1-henning.schild@siemens.com> (raw)

Issue: when S=$WORKDIR/dir1/source/ instead of $WORKDIR/source/
do_deploy_deb will not be able to find the *.debs to put into the
isar-apt repo.

dpkg-buildpackage will always place the packages in the parent directory
"..", so use S/.. instead of WORKDIR to locate them.

Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
 meta/classes/dpkg-base.bbclass | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta/classes/dpkg-base.bbclass b/meta/classes/dpkg-base.bbclass
index 3845d8c..75b45a7 100644
--- a/meta/classes/dpkg-base.bbclass
+++ b/meta/classes/dpkg-base.bbclass
@@ -66,7 +66,7 @@ do_build() {
 CLEANFUNCS += "repo_clean"
 
 repo_clean() {
-    PACKAGES=$(cd ${WORKDIR}; ls *.deb | sed 's/\([^_]*\).*/\1/')
+    PACKAGES=$(cd ${S}/..; ls *.deb | sed 's/\([^_]*\).*/\1/')
     if [ -n "${PACKAGES}" ]; then
         reprepro -b ${DEPLOY_DIR_APT}/${DISTRO} \
                  --dbdir ${DEPLOY_DIR_DB}/${DISTRO} \
@@ -83,10 +83,11 @@ do_deploy_deb() {
              --dbdir ${DEPLOY_DIR_DB}/${DISTRO} \
              -C main \
              includedeb ${DEBDISTRONAME} \
-             ${WORKDIR}/*.deb
+             ${S}/../*.deb
 }
 
 addtask deploy_deb after do_build
 do_deploy_deb[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}"
 do_deploy_deb[lockfiles] = "${DEPLOY_DIR_APT}/isar.lock"
 do_deploy_deb[depends] = "isar-apt:do_cache_config"
+do_deploy_deb[dirs] = "${S}"
-- 
2.16.1


             reply	other threads:[~2018-05-14 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 15:34 Henning Schild [this message]
2018-05-15 15:34 ` Alexander Smirnov

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=20180514153442.1409-1-henning.schild@siemens.com \
    --to=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