From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6450015460633083904 X-Received: by 10.25.31.212 with SMTP id f203mr2086056lff.22.1503321942765; Mon, 21 Aug 2017 06:25:42 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.25.213.79 with SMTP id m76ls605071lfg.25.gmail; Mon, 21 Aug 2017 06:25:42 -0700 (PDT) X-Received: by 10.46.1.227 with SMTP id f96mr2247409lji.23.1503321942110; Mon, 21 Aug 2017 06:25:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1503321942; cv=none; d=google.com; s=arc-20160816; b=q65K6lD3oLnIihar8PpYjxjq13jxfG3rC4YJRG+o9B3QnNLl4f+B/rcpkWQ8LYXZ/7 cO0S48jlZN8TkHd0++g8GJkV2v1CsCLCe2Ezaf5HT1v+Yfxh3Qe35knA0WNu22bUwtT0 gTasdrmnrz/wy3rWOzLlhrqxDhlHieqpwi6VvJbae7IZEjg5erEx+kFij9PKQtkDvKZS yXlxgd4GZy3zMtB1himuAahIy0FNrMH4MEaNCaRQn5vUhfaHxBcCV/7yA41ndvDeS0OU eJXjYBwvpuzgsJVSchnHFAdMoJLkk7uscdHxpoT1yaKFYU2AbbF4nZt8zqfN/Knz5apF EYAg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date :arc-authentication-results; bh=fr4OEqKM0b8HE9rTzPdrpqyqmiPRfLFaHR4UaiRis/k=; b=rvuDGbF7kcP0N3pVL1Cavy3cFndYTOwR28JAJWKbUSmvlrbMPqHVNU8K+DICCpjH7S IqEIW4siG9uju4Ud8QaseNpZnZ3mKon9uVBQ3HJW+7JqShtl4viHFf/KyWjZiEESrNk7 o3ZvaZPvpiDBmadzsLchQT7brit3CEkejf0O7GZGXtosgaWToCkMo5up9XcBS3770sqp 8cda0PkYZy8Rda3keq7tmgkgoWDGy5VhmJXUlg6G6vUzDsg6/mbwfY+qtWMx7kA0UEi3 OQjBNDJZIc+ql53gKMaaufYvWKOani7LyvlldBjLqBV2sqrJWtfCXKsWyAjCEt3LSuyq sUYQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id 192si86557wmy.2.2017.08.21.06.25.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Aug 2017 06:25:41 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.radix50.net (p5B2DC546.dip0.t-ipconnect.de [91.45.197.70]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id v7LDPdvU008403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 21 Aug 2017 15:25:41 +0200 Received: from yssyq.radix50.net (localhost [127.0.0.1]) by yssyq.radix50.net (8.14.4/8.14.4/Debian-8) with ESMTP id v7LDPdl2021480 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 21 Aug 2017 15:25:39 +0200 Received: (from ibr@localhost) by yssyq.radix50.net (8.14.4/8.14.4/Submit) id v7LDPdT7021479 for isar-users@googlegroups.com; Mon, 21 Aug 2017 15:25:39 +0200 Date: Mon, 21 Aug 2017 15:25:39 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH 0-10 of 16 v2 4/8] meta: conf: use bitbake.conf from bitbake and apply local changes Message-ID: <20170821132539.GD8387@yssyq.radix50.net> Mail-Followup-To: isar-users@googlegroups.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-TUID: PR1YWTNB3woU On Thu, Aug 03, 2017 at 01:55:53PM +0200, Henning Schild wrote: > force isar to always use a bitbake.conf from its bitbake > the diff went into a file that needs to be looked at later Applied with comment amendments, thanks. Alex has updated the commit comment to reflect also the motivation for the change. In the commit comment, please use complete sentences (first cap, period at the end). We had considered the split configuration in the beginning and have seen that 1. Yocto forks it, and 2. bitbake doesn't seem to support reading both by itself. These were the reasons why we also forked the file. (1) might be caused by the fact that there are no major bitbake users except Yocto, so both are possibly not clearly separated. The separation has value for Isar, since it clearly shows what is different, that is why I've applied the patch. (2) is worse, as IMHO, bitbake should do that itself and it doesn't (https://github.com/ilbers/isar/issues/27). Concatenating configs is magic that Yocto users do not expect, and this has to be documented. Could you provide a patch for the manual? With kind regards, Baurzhan.