public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>, Frank Lenormand <flenormand@ilbers.de>
Subject: Re: [PATCH 4/4] buildchroot: Update build script.
Date: Tue, 8 Aug 2017 13:05:16 +0200	[thread overview]
Message-ID: <20170808130516.6fbd4cc4@md1em3qc> (raw)
In-Reply-To: <20170808100424.19607-5-asmirnov@ilbers.de>

Looks good, but this whole script should go into dpkg-src.bbclass into
the task where it gets called. Less indirection, files and confusion.

Henning

Am Tue, 8 Aug 2017 13:04:24 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:

> From: Frank Lenormand <flenormand@ilbers.de>
> 
> Handle the `package [arch]` syntax in Debian's `Build-Depends` field.
> 
> Signed-off-by: Frank Lenormand <flenormand@ilbers.de>
> ---
>  meta/recipes-devtools/buildchroot/files/build.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-devtools/buildchroot/files/build.sh
> b/meta/recipes-devtools/buildchroot/files/build.sh index
> ba443bc..19d554e 100644 ---
> a/meta/recipes-devtools/buildchroot/files/build.sh +++
> b/meta/recipes-devtools/buildchroot/files/build.sh @@ -9,7 +9,7 @@ cd
> $1 # Get list of dependencies manually. The package is not in apt, so
> no apt-get # build-dep. dpkg-checkbuilddeps output contains version
> information and isn't # directly suitable for apt-get install.
> -DEPS=`perl -ne 'next if /^#/; $p=(s/^Build-Depends:\s*/ / or (/^ /
> and $p)); s/,|\n|\([^)]+\)//mg; print if $p' < debian/control`
> +DEPS=`perl -ne 'next if /^#/; $p=(s/^Build-Depends:\s*/ / or (/^ /
> and $p)); s/,|\n|\([^)]+\)|\[[^]]+\]//mg; print if $p' <
> debian/control` # Install deps apt-get install -y $DEPS


  reply	other threads:[~2017-08-08 11:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 10:04 [PATCH 0/4] Various fixes Alexander Smirnov
2017-08-08 10:04 ` [PATCH 1/4] isar: Fix mutli-distro builds in parallel Alexander Smirnov
2017-08-08 10:58   ` Henning Schild
2017-08-08 11:21     ` Alexander Smirnov
2017-08-08 11:56       ` Henning Schild
2017-08-21 21:11   ` Baurzhan Ismagulov
2017-08-08 10:04 ` [PATCH 2/4] scripts: Update start_vm Alexander Smirnov
2017-08-08 10:04 ` [PATCH 3/4] buildchroot: Fix dependency installation in buildchroot Alexander Smirnov
2017-08-21 21:28   ` Baurzhan Ismagulov
2017-08-08 10:04 ` [PATCH 4/4] buildchroot: Update build script Alexander Smirnov
2017-08-08 11:05   ` Henning Schild [this message]
2017-08-21 21:42     ` Baurzhan Ismagulov
2017-08-21 21:35   ` 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=20170808130516.6fbd4cc4@md1em3qc \
    --to=henning.schild@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=flenormand@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