public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH 0/1] avoid user prompts when mk-build-deps is called
Date: Thu, 25 Jan 2018 21:36:54 +0100	[thread overview]
Message-ID: <20180125203655.6894-1-Cedric_Hombourger@mentor.com> (raw)

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 their installation but would fail when
called from bitbake (no stdin). Override the default install command to add
the -y switch (assume yes).

Cedric Hombourger (1):
  build.sh: eliminate potential prompts from mk-build-deps/apt-get

 meta/recipes-devtools/buildchroot/files/build.sh | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

-- 
2.11.0


             reply	other threads:[~2018-01-25 20:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 20:36 Cedric_Hombourger [this message]
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
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=20180125203655.6894-1-Cedric_Hombourger@mentor.com \
    --to=cedric_hombourger@mentor.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