From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6618191789727678464 X-Received: by 2002:a17:906:1c45:: with SMTP id l5-v6mr1120251ejg.3.1541502867411; Tue, 06 Nov 2018 03:14:27 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:1d53:: with SMTP id o19-v6ls754016ejh.0.gmail; Tue, 06 Nov 2018 03:14:26 -0800 (PST) X-Google-Smtp-Source: AJdET5dx6Z07SWMZJ4wlkv04CfO3WbQefs5hK+abDKSdtxk5I//3AwKB9a+O6KRrP3z8Ai283hBa X-Received: by 2002:a17:906:328b:: with SMTP id 11-v6mr3126958ejw.14.1541502866852; Tue, 06 Nov 2018 03:14:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541502866; cv=none; d=google.com; s=arc-20160816; b=Aj4Jh85dcDo4CyA7r2b1hxn8HMZYX0bEzFWyapUJ/qZz9wn6dC/6umZptNMsdyp1Bk NYAhRqPIZDiM3LcDrOdquJBpe6NMoSkQplQSvFJF3rNdCpLXpMi1MAbP4vBV8vuKXf2I C9GLdXOnCQKr6I3/BA8dh0CNDDYV3vcsr8ugu0LmcJ1QHAaJkm6YTJo7ZrKy9kUT2P/Y Lc9Wq6nr5h/znauifk6VnUfGBPsWcpfntPJk7VIh5RYWLGYN8S/lwPcXjPPp8e3EwtG9 +TY8sRC051xToKEfguRMYhPJn3lcrn/8ad7k05LA1OyPMMBH0lzE3oV5rrooFLjRhM1O xyvg== 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=gO3u395I2b1Rznmnmd2UR2VO/SrOyHCYlcN6DggYnhc=; b=BN+hoO9h3mWXh9pN8s7UXbQoF/rhT9s+iSJLRvOkINOs0UW1eOQsxPow2SvcDo5cW1 F4KOiVIz/p9gko4jw+ASZpwcP8Y+Zwd7bEoxG6uYOs4xm2hjOxym3OICNT/hQ80FxOXL n5N3+rPwVl4IL4Efs9nZxjWAvjalkocOZ0QgTcDUwyjL5ngRlERwaRsfaYeg5K/JuhZm U1wjGWngbwUDLH6fMP8z+8bQztsJQKv9Gu1H65iWfI8V5EpiVe4LradIFS/UtjGS0SKG nPq9D8UK4GGNZrr44Z8BsHI2SZ2kmbKIXUFnNv56dBTI0DDBv4AnMMx8f5WF0/yT7osc JjIw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id c7-v6si333337edi.2.2018.11.06.03.14.26 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Nov 2018 03:14:26 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id wA6BEQOK031075 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 6 Nov 2018 12:14:26 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id wA6BEPf2031604; Tue, 6 Nov 2018 12:14:25 +0100 Subject: Re: [PATCH] bitbake: Allow setting DL_DIR from environment To: Harald Seiler , isar-users@googlegroups.com References: <106c00a92881b8fefff5616e27c7c434c2c4983e.camel@denx.de> From: Jan Kiszka Message-ID: <09b4d369-b3bf-0e2e-7d1e-47b1660d555e@siemens.com> Date: Tue, 6 Nov 2018 12:14:24 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: n/f1iz9DbzeZ On 06.11.18 12:06, Harald Seiler wrote: > On Wed, 2018-10-31 at 07:39 +0100, Jan Kiszka wrote: >> On 30.10.18 17:44, Harald Seiler wrote: >>> This patch allows adding DL_DIR to BB_ENV_EXTRAWHITE >>> and then specifying a custom DL_DIR in the environment. >>> >>> This behavior mirrors the one in poky. >>> >>> Signed-off-by: Harald Seiler >>> --- >>> bitbake/conf/bitbake.conf | 2 +- >> >> We do not patch bitbake so far. Is this fix in upstream already? Then let's >> fast-forward bitbake to that revision. If not, send it upstream first. Local, >> isar-specific changes go to isar-bitbake.conf. > > Upstream (bitbake) does not have this fix. The reason it works in poky is that > they have removed the `bitbake/conf/bitbake.conf` file completely and instead > use their own config in `meta/conf/bitbake.conf`. > > I am not sure why this is done this way, though. > Then I would say - in order to keep bitbake/ clean - we should promote isar-bitbake.conf to the only bitbake.conf we use, migrating current bitbake.conf content over. But maybe it is still worth try to convince upstream bitbake of this tiny change. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux