public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Harald Seiler <hws@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] bitbake: Allow setting DL_DIR from environment
Date: Tue, 06 Nov 2018 12:06:10 +0100	[thread overview]
Message-ID: <eedb17e3199deb609291eb0dae8cf090db826416.camel@denx.de> (raw)
In-Reply-To: <bad4755f-4246-9d22-f981-0847e7dacb93@siemens.com>

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 <hws@denx.de>
> > ---
> >   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.

> 
> >   meta/conf/isar-bitbake.conf | 2 +-
> >   2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/bitbake/conf/bitbake.conf b/bitbake/conf/bitbake.conf
> > index a460df4..ba0d68b 100644
> > --- a/bitbake/conf/bitbake.conf
> > +++ b/bitbake/conf/bitbake.conf
> > @@ -23,7 +23,7 @@ CVSDIR = "${DL_DIR}/cvs"
> >   DEPENDS = ""
> >   DEPLOY_DIR = "${TMPDIR}/deploy"
> >   DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images"
> > -DL_DIR = "${TMPDIR}/downloads"
> > +DL_DIR ?= "${TMPDIR}/downloads"
> >   FILESPATH = "${FILE_DIRNAME}/${PF}:${FILE_DIRNAME}/${P}:${FILE_DIRNAME}/${PN}:${FILE_DIRNAME}/files:${FILE_DIRNAME}"
> >   FILE_DIRNAME = "${@os.path.dirname(d.getVar('FILE', False))}"
> >   GITDIR = "${DL_DIR}/git"
> > diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/isar-bitbake.conf
> > index 666c4a3..39e73f6 100644
> > --- a/meta/conf/isar-bitbake.conf
> > +++ b/meta/conf/isar-bitbake.conf
> > @@ -19,7 +19,7 @@
> >   # OTHER DEALINGS IN THE SOFTWARE.
> >   
> >   WORKDIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/${PF}"
> > -DL_DIR = "${TOPDIR}/downloads"
> > +DL_DIR ?= "${TOPDIR}/downloads"
> >   SSTATE_DIR ?= "${TMPDIR}/sstate-cache"
> >   BUILDCHROOT_HOST_DIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot-host/rootfs"
> >   BUILDCHROOT_TARGET_DIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot-target/rootfs"
> > --
> > 2.14.1
> > 
> 

-- 
Harald

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-62  Fax: +49-8142-66989-80   Email: hws@denx.de 


  parent reply	other threads:[~2018-11-06 11:06 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   ` Harald Seiler [this message]
2018-11-06 11:14     ` [PATCH] bitbake: Allow setting DL_DIR from environment Jan Kiszka
2018-11-09 14:11     ` Baurzhan Ismagulov

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=eedb17e3199deb609291eb0dae8cf090db826416.camel@denx.de \
    --to=hws@denx.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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