Re: Upgrading bitbake in isar

[Henning Schild <henning.schild@siemens.com>]

Hi,

i already did that a few months ago and just went for latest-greatest.
And as expected that worked without much headache, after all it is only
our build tool which seems to be mostly backward compatible.
I remember a few warnings that would probably have required recipe
updates to silence them, but it did build on the first try (even the
whole thing in your CI). After that i spent some time on wic, which was
not that easy.

So i suggest "1.40". If you hit any blocking points a lower version
might also be ok, but i would not expect any. The trickier thing would
be to make Isar properly use the new bitbake after the bump. (using new
features, removing workarounds and alike).

Henning

Am Thu, 1 Nov 2018 13:45:20 +0300
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:

> Hi everybody,
> 
> I had several times requests regarding bitbake's upgrade in isar.
> Do you have any suggestions about bitbake's revision to fast-forward?
> 
> Kind regards,
> Maxim.
> 
> -------- Forwarded Message --------
> Subject: Re: [PATCH] bitbake: Allow setting DL_DIR from environment
> Date: Wed, 31 Oct 2018 07:39:01 +0100
> From: Jan Kiszka <jan.kiszka@siemens.com>
> To: Harald Seiler <hws@denx.de>, isar-users@googlegroups.com
> 
> 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.
> 
> Jan
> 
> >   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 
>