public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] build.sh: eliminate user prompts from mk-build-deps
Date: Fri, 26 Jan 2018 08:48:49 +0100	[thread overview]
Message-ID: <0a9e0a97-67e5-8423-166c-6165ac78eaae@siemens.com> (raw)
In-Reply-To: <861d9e48f45a420da79d40b67e95782a@svr-ies-mbx-02.mgc.mentorg.com>

On 2018-01-26 08:47, Hombourger, Cedric wrote:
> Hi Jan,
> 
> If I am not mistaken these args were already passed before according to mk-build-deps (1); more specifically:
> 
> -t, --tool
>     When installing the generated package use the specified tool. (default: apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends)
> 
> I have carried them over to make sure we only add -y.

Ah, sorry, then it's fine.

Jan

> 
> Cedric
> 
> 
> -----Original Message-----
> From: Jan Kiszka [mailto:jan.kiszka@siemens.com] 
> Sent: Friday, January 26, 2018 8:42 AM
> To: Hombourger, Cedric <Cedric_Hombourger@mentor.com>; isar-users@googlegroups.com
> Subject: Re: [PATCH 1/1] build.sh: eliminate user prompts from mk-build-deps
> 
> On 2018-01-25 21:36, Cedric_Hombourger@mentor.com wrote:
>> 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 | 5 ++++-
>>  1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-devtools/buildchroot/files/build.sh 
>> b/meta/recipes-devtools/buildchroot/files/build.sh
>> index 975252e..760ebc8 100644
>> --- a/meta/recipes-devtools/buildchroot/files/build.sh
>> +++ b/meta/recipes-devtools/buildchroot/files/build.sh
>> @@ -6,8 +6,11 @@
>>  # Go to build directory
>>  cd $1
>>  
>> +# Install command to be used by mk-build-deps (use -y for 
>> +non-interactive) install_cmd="apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y"
> 
> This sneaks in --no-install-recommends, which has a value, but it should be separated out or at least mentioned.
> 
> Also, Debug::pkgProblemResolver=yes is worth mentioning, even when it doesn't change the outcome of the installation.
> 
> Jan
> 
>> +
>>  # 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
>>
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
> 


-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-01-26  7:48 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 [this message]
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=0a9e0a97-67e5-8423-166c-6165ac78eaae@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=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