public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] bitbake: Allow setting DL_DIR from environment
Date: Fri, 9 Nov 2018 15:11:13 +0100	[thread overview]
Message-ID: <20181109141113.GF17039@yssyq.m.ilbers.de> (raw)
In-Reply-To: <eedb17e3199deb609291eb0dae8cf090db826416.camel@denx.de>

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.

      parent reply	other threads:[~2018-11-09 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 16:44 Harald Seiler
2018-10-31  6:13 ` chombourger
2018-10-31  6:39 ` Jan Kiszka
2018-11-01 10:45   ` Upgrading bitbake in isar Maxim Yu. Osipov
2018-11-02  9:55     ` Henning Schild
2018-11-06 11:06   ` [PATCH] bitbake: Allow setting DL_DIR from environment Harald Seiler
2018-11-06 11:14     ` Jan Kiszka
2018-11-09 14:11     ` Baurzhan Ismagulov [this message]

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=20181109141113.GF17039@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --cc=isar-users@googlegroups.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