From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6739560601010307072 X-Received: by 2002:a05:600c:2252:: with SMTP id a18mr224670wmm.141.1569864383537; Mon, 30 Sep 2019 10:26:23 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:1a96:: with SMTP id a144ls74761wma.3.gmail; Mon, 30 Sep 2019 10:26:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqyobeyAEr/d7nBpjwlbSr+Rd3spZ7NVQBsUxTVJ3dChU4s6bicFaW3JGqiCfm6W44j0Gmg0 X-Received: by 2002:a1c:5444:: with SMTP id p4mr235723wmi.69.1569864382968; Mon, 30 Sep 2019 10:26:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569864382; cv=none; d=google.com; s=arc-20160816; b=bt7PNg+y6bNYrb3AnGQkN4WSOm8mlbGE2r6ft4UKl98YZYsjS/PMz7a29kJgKWenMd Ju30XM5ABczZw0LKCg/PfjYRR4CRV37E2IIp6hs7PDMZxCx6M084ITHR1J4ZANxt9LmA fjMUYimNnUkdC1UesXG1zPFWXrEKIatLdTGIhNcvZkLmTszOkVybJfodObc/9fqXGtdf qH3WwcRwMXi9zB22yJblQvlibssoJKIpO+XbHT4M7nFcTLEeE++Or63u8W3Wp7Mb5ooR 1zD2cVSFS4AU0owGtvnV+1Jvciia4hA3gqlDkXWFE6XwuBRSh1dg6ipe1WcK3oPsIary 5EzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject; bh=MWnQ1vH7vKa4NgEDDvq907MTUEbRG27nsB5Y2tzWtic=; b=D0sFS6SxNdTlMJlmim6FZjC0+CKod/fxGieacY7dtMnRP5fSg6zzl1iHqt0ULRdV4E HkH6f4rL+7UvvmGsgegNBwd0HMtPkarkzPai/gyQkeQWfP9Gpy6VEGODGcFKvkrFdyrf IRvtZLiNCQtJxIyxp+XLjLWB7TzjHUY6HipCOhmmZjgAco6pXz+UA4VgN++Sb9hunZwI VtVUiROQtTzpFnuM/nM9K5UTyXOLy8flA5+MpaW2XCWQ/xYDLVZAbfR3VSNXNkFiCJaV Fh6kUOcPeTQ5otW5P+VvQuuQGsYSQPohWyK4ktQ0ON9EWHBOKYySxVD44QkIDLk3y+Rk miOA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id n16si786531wrs.4.2019.09.30.10.26.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Sep 2019 10:26:22 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x8UHQM9b010956 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 30 Sep 2019 19:26:22 +0200 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x8UHQMYU030778 for ; Mon, 30 Sep 2019 19:26:22 +0200 Subject: Re: [PATCH v6 12/27] Detect false sharing of recipes To: isar-users References: <5a2e329b881ec0b392d0f1abd116f1deeee0f66f.1569176231.git.jan.kiszka@siemens.com> <20190929145700.ads3zbq7hz77olcw@yssyq.m.ilbers.de> <248aa6db-6327-9604-40b6-e7135a5f9961@siemens.com> <20190930095610.shyewhozb46dautr@yssyq.m.ilbers.de> <20190930145326.prsfzcxogzebwbll@yssyq.m.ilbers.de> <5cb07f77-c81f-53ee-7b4c-183e5609ae4c@siemens.com> <20190930153937.n4rvim46yz7k2vc4@yssyq.m.ilbers.de> <20190930172048.ihogbjrmsysur4a3@yssyq.m.ilbers.de> From: Jan Kiszka Message-ID: Date: Mon, 30 Sep 2019 19:26:22 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190930172048.ihogbjrmsysur4a3@yssyq.m.ilbers.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: W4okXz4e1sNC On 30.09.19 19:20, Baurzhan Ismagulov wrote: > On Mon, Sep 30, 2019 at 06:34:02PM +0200, Jan Kiszka wrote: >> The differences can come from different HOST_DISTRO_* settings. Those are >> applied on a per target distro/arch basis. > > I see, thanks for the info. > > I wonder whether those could be moved down to buildchroot / images in the > future. > Would mean breaking up the only-once repo updates into chunks so that everything we need in addition can also be pulled later on, but still only once. But it may not be trivial. > >> Locking papered over this. And it broke rebuilding on changes. > > The implementation was broken, no question. Your patches are necessary to > provide the correct behavior and will be merged. > > The question was rather an open one beyond the series, whether one could > determine whether there are no differences and keep sharing in that case -- I > don't have an answer ATM. Honestly, I think we have more urgent issues. Correctness first, and then - when there is a real need - we can think of optimization. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux