From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 4/6] Enable proper rebuilds on dependency changes
Date: Tue, 13 Feb 2018 16:03:19 +0300 [thread overview]
Message-ID: <73bd323b-0dc2-a84a-ae5a-59177cfe6921@ilbers.de> (raw)
In-Reply-To: <7d0504da7640612abded5ffe1e1b3c6d10168b49.1518422347.git.jan.kiszka@siemens.com>
On 02/12/2018 10:59 AM, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Install a basichash as signature handler and set the stamp policy to
> full - and suddenly we get proper rebuilds of the image and all affected
> packages when some recipe down the dependency chain changed!
>
> We are using the legacy bitbake mechanism here as we do not have
> setscene machinery like OE. Still good enough for us.
>
BTW: have you tried this? Two years ago I tried it in Yocto and it
didn't work properly, not all the dependents were rebuilt. If it works,
it's a very good feature!
Also do you know if this feature relies on DEPENDS variable? If so, we
should keep this in mind with the idea to drop DEPENDS from recipes.
Alex
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> meta/conf/isar-bitbake.conf | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/isar-bitbake.conf
> index 660e0c0..c01e486 100644
> --- a/meta/conf/isar-bitbake.conf
> +++ b/meta/conf/isar-bitbake.conf
> @@ -37,9 +37,8 @@ BB_HASHCONFIG_WHITELIST ?= "${BB_HASHBASE_WHITELIST} DATE TIME SSH_AGENT_PID \
> GIT_PROXY_COMMAND ALL_PROXY all_proxy NO_PROXY no_proxy FTP_PROXY ftp_proxy \
> HTTP_PROXY http_proxy HTTPS_PROXY https_proxy SOCKS5_USER SOCKS5_PASSWD \
> BB_SETSCENE_ENFORCE BB_CMDLINE BB_SERVER_TIMEOUT"
> -
> -# Setup our default hash policy
> -BB_SIGNATURE_HANDLER ?= "noop"
> +BB_SIGNATURE_HANDLER ?= "basichash"
> +BB_STAMP_POLICY ?= "full"
>
> # Add event handlers for bitbake
> INHERIT += "isar-events"
>
next prev parent reply other threads:[~2018-02-13 13:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 7:59 [PATCH 0/6] Add support for automatic partial rebuilds on recipe changes Jan Kiszka
2018-02-12 7:59 ` [PATCH 1/6] Fix indention of base_do_build Jan Kiszka
2018-02-12 7:59 ` [PATCH 2/6] Add clean and cleanall tasks Jan Kiszka
2018-02-13 12:49 ` Alexander Smirnov
2018-02-13 12:51 ` Jan Kiszka
2018-02-12 7:59 ` [PATCH 3/6] Enable recipe caching Jan Kiszka
2018-02-12 7:59 ` [PATCH 4/6] Enable proper rebuilds on dependency changes Jan Kiszka
2018-02-13 13:03 ` Alexander Smirnov [this message]
2018-02-13 16:21 ` Jan Kiszka
2018-02-13 17:57 ` Jan Kiszka
2018-02-13 18:08 ` Alexander Smirnov
2018-02-13 18:44 ` Jan Kiszka
2018-02-13 19:02 ` Alexander Smirnov
2018-02-13 19:22 ` Jan Kiszka
2018-02-13 19:38 ` Alexander Smirnov
2018-02-13 20:04 ` Jan Kiszka
2018-02-12 7:59 ` [PATCH 5/6] dpkg-raw: Clean DEBIAN dir prior to filling it Jan Kiszka
2018-02-13 14:06 ` Alexander Smirnov
2018-02-13 16:22 ` Jan Kiszka
2018-02-13 16:31 ` Alexander Smirnov
2018-02-13 16:33 ` Jan Kiszka
2018-02-12 7:59 ` [PATCH 6/6] isar-image-base: Clean rootfs folder prior to building Jan Kiszka
2018-02-13 13:49 ` Alexander Smirnov
2018-02-13 16:24 ` Jan Kiszka
2018-02-13 7:40 ` [PATCH 0/6] Add support for automatic partial rebuilds on recipe changes Jan Kiszka
2018-02-13 14:01 ` Alexander Smirnov
2018-02-13 16:28 ` Jan Kiszka
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=73bd323b-0dc2-a84a-ae5a-59177cfe6921@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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