From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <Cedric_Hombourger@mentor.com>, <isar-users@googlegroups.com>
Subject: Re: [PATCH v2] build.sh: eliminate potential prompts from mk-build-deps/apt-get
Date: Tue, 30 Jan 2018 21:51:53 +0100 [thread overview]
Message-ID: <20180130215153.633d8bec@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <20180129191746.25ba70e0@mmd1pvb1c.ad001.siemens.net>
498b128 is still in next and could be fixed before hitting master. I am
all for keeping history, even if it contains mistakes so we just not
squash them.
Alex make sure to update the comment, should the hash change.
Henning
Am Mon, 29 Jan 2018 19:17:46 +0100
schrieb "[ext] Henning Schild" <henning.schild@siemens.com>:
> Thanks!
>
> Henning
>
> Am Mon, 29 Jan 2018 17:31:05 +0100
> schrieb <Cedric_Hombourger@mentor.com>:
>
> > From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> >
> > commit 498b128 caused build dependencies to be installed via
> > mk-build-deps.
> >
> > The tool may ask the user to confirm installation of the
> > dependencies but would fail when called from bitbake (no stdin).
> > Override the default install command to add the -y switch to the
> > apt-get command it uses.
> >
> > Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> > ---
> > meta/recipes-devtools/buildchroot/files/build.sh | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-devtools/buildchroot/files/build.sh
> > b/meta/recipes-devtools/buildchroot/files/build.sh index
> > 975252e..77e0fdd 100644 ---
> > a/meta/recipes-devtools/buildchroot/files/build.sh +++
> > b/meta/recipes-devtools/buildchroot/files/build.sh @@ -6,8 +6,14 @@
> > # Go to build directory
> > cd $1
> >
> > +# Install command to be used by mk-build-deps
> > +# Notes:
> > +# 1) everything before the -y switch is unchanged from the
> > defaults +# 2) we add -y to go non-interactive
> > +install_cmd="apt-get -o Debug::pkgProblemResolver=yes
> > --no-install-recommends -y" +
> > # Install all build deps
> > -mk-build-deps -i -r debian/control
> > +mk-build-deps -t "${install_cmd}" -i -r debian/control
> >
> > # If autotools files have been created, update their timestamp to
> > # prevent them from being regenerated
>
next prev parent reply other threads:[~2018-01-30 20:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 20:36 [PATCH 0/1] avoid user prompts when mk-build-deps is called Cedric_Hombourger
2018-01-25 20:36 ` [PATCH 1/1] build.sh: eliminate user prompts from mk-build-deps Cedric_Hombourger
2018-01-26 7:42 ` Jan Kiszka
2018-01-26 7:47 ` Hombourger, Cedric
2018-01-26 7:48 ` Jan Kiszka
2018-01-29 10:25 ` Henning Schild
2018-01-29 16:31 ` [PATCH v2] build.sh: eliminate potential prompts from mk-build-deps/apt-get Cedric_Hombourger
2018-01-29 18:17 ` Henning Schild
2018-01-30 20:51 ` Henning Schild [this message]
2018-01-29 13:49 ` [PATCH 0/1] avoid user prompts when mk-build-deps is called Alexander Smirnov
2018-01-29 15:59 ` Henning Schild
2018-01-29 16:14 ` Alexander Smirnov
2018-02-03 9:49 ` chombourger
2018-02-03 17:37 ` Alexander Smirnov
2018-02-04 8:08 ` chombourger
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=20180130215153.633d8bec@mmd1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=asmirnov@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