public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: chombourger@gmail.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] bitbake: Allow setting DL_DIR from environment
Date: Tue, 30 Oct 2018 23:13:36 -0700 (PDT)	[thread overview]
Message-ID: <9b3d1c8c-8115-4a0f-8c9f-e796ef36b372@googlegroups.com> (raw)
In-Reply-To: <106c00a92881b8fefff5616e27c7c434c2c4983e.camel@denx.de>


[-- Attachment #1.1: Type: text/plain, Size: 1699 bytes --]

Looks good to me

On Tuesday, October 30, 2018 at 5:44:14 PM UTC+1, 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 <h...@denx.de <javascript:>> 
> --- 
>  bitbake/conf/bitbake.conf   | 2 +- 
>  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 
>
>

[-- Attachment #1.2: Type: text/html, Size: 2347 bytes --]

  reply	other threads:[~2018-10-31  6:13 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 [this message]
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

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=9b3d1c8c-8115-4a0f-8c9f-e796ef36b372@googlegroups.com \
    --to=chombourger@gmail.com \
    --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