From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6618191789727678464 X-Received: by 2002:ac2:42d0:: with SMTP id n16mr602092lfl.5.1541772677157; Fri, 09 Nov 2018 06:11:17 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:5b0c:: with SMTP id p12-v6ls156488ljb.19.gmail; Fri, 09 Nov 2018 06:11:16 -0800 (PST) X-Google-Smtp-Source: AJdET5cYkUp6p33z2VfoOTJxld59JaJlelOJF4813o+LVbKEHLVMeIzSqvGcHRTF+q5xybjnpG/I X-Received: by 2002:a2e:9902:: with SMTP id v2-v6mr916379lji.6.1541772676633; Fri, 09 Nov 2018 06:11:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541772676; cv=none; d=google.com; s=arc-20160816; b=fUW/Y/SSTJUnheerp7bzYYfZYsj42poj6Yz9e/mIPsKO2UaexMn/H9tpZ920h1uyaf dyrSSc6MIIVmoeqqTCE9qeaFgzOuomYqkalRX5SqDvkZJAC/o8b38aDaZMUzIKOm++Q3 XPY3lTQTgm67uJpns+tWLTmA1PIIh7oHW44Knem5KiTShjyVUMkN3lFAMWpl+gf9SJRz eG+KJdV/t8cmuV6B8M/DMQLbjPBzLF+i3hOdiyphkNad/p5Sau8MNQvrkqY1wEylt7eS tYUSXE3lMTLVywdi5CG9pUtPaFXkiP4EZx3HgSMCfp7ASNUIBccdGXY8vgq3n8LF028L +b/w== 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; bh=jY7eCsp5FrxeijDnfGEJhL4m8UqdT5O200sHjFWTl2A=; b=zGPSY4A7kE3fuAIoZE0kvPNDS+3WV/g//vwlgz9B7l9GzE6VwI1E+1WkMDYyeacbpB ARQlI6xrL5X9b0QKajvG/N50O5whafzCsFXKRmd5HAogDgXWGf2dxPWKeTX9bpX7KIpo 1J55Lri6CqHf9aOZlekjjOKiZcWUu3XTBm6RGKB1JHMGzduIWO0dQpnOviuMMnuQVRyR yLKZ4JzSEvzZzuPAh2k1jhBLVRojD9A9Z99y6wCdO70xuGb9oiLfOmtQaHgf/bs+pqdT KK7uJttjzOpq82zch6c+ZwIzx4FqziEJ1luXejBgipdpvK0NB9arRjRmyNV+vvzCBm/B nefA== 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 w13-v6si308820lfe.3.2018.11.09.06.11.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Nov 2018 06:11:16 -0800 (PST) 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.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id wA9EBDwe016217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 9 Nov 2018 15:11:15 +0100 Received: from yssyq.m.ilbers.de (localhost [127.0.0.1]) by yssyq.m.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPS id wA9EBDWP029953 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 9 Nov 2018 15:11:13 +0100 Received: (from ibr@localhost) by yssyq.m.ilbers.de (8.15.2/8.15.2/Submit) id wA9EBDOS029952 for isar-users@googlegroups.com; Fri, 9 Nov 2018 15:11:13 +0100 Date: Fri, 9 Nov 2018 15:11:13 +0100 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH] bitbake: Allow setting DL_DIR from environment Message-ID: <20181109141113.GF17039@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com References: <106c00a92881b8fefff5616e27c7c434c2c4983e.camel@denx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-TUID: e2jawDCf0zuC On Tue, Nov 06, 2018 at 12:06:10PM +0100, Harald Seiler wrote: > 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`. This is how it was originally implemented in Isar, due to the fact that upstream uses it that way. Later, this was changed with the goal of keeping Isar modifications thin and ease bitbake upgrades. Of course, this will only work if the upstream plays along. > I am not sure why this is done this way, though. I have an impression that the distinction "bitbake vs. OE / Yocto" upstream is blurred and doesn't play big role, since the latter is being assumed the single user. It would indeed be interesting to submit the change upstream and see the feedback. With kind regards, Baurzhan.