Environment variable DL_DIR being overwritten about isar

[henning-schild]

In fact there are two assignments using the = operator in build/conf/bitbake.conf but one of them is coming from upstream bitbake. Are you sure your expectation is correct and whatever you are trying to do would work i.e. in openembedded?

[Silvanoc]

Are you sure your expectation is correct and whatever you are trying to do would work i.e. in openembedded?

I have to admit, that I never checked it.

But I appear not to be the only one with that expectation. Since the project KAS is giving the environment variable DL_DIR enough importance to pass it to bitbake. See the documentation here and the code here.

@igaw you initially implemented support for it on KAS, does it mean that you agree on my expectation? 😃

[igaw]

kas passes DL_DIR through and those Yocto project I am working on honor the environment variable. Why should DL_DIR be hard coded in the project. That doesn't make sense to me. This is something the build setup needs to control not the upstream project.

[Silvanoc]

According to the bitbake upstream documentation, this variable should be honored. So I would expect ISAR also to honor it too. Since ISAR is not honoring it, I would expect it to be either a bitbake bug or an ISAR bug.

In fact there are two assignments using the = operator in build/conf/bitbake.conf but one of them is coming from upstream bitbake.

@henning-schild do you mean this for Bitbake and this for ISAR?

[henning-schild]

Isar does not use issues ... should not have commented in the first place. Please get in touch over the mailinglist

[Silvanoc]

@henning-schild you're right. Too much context switching with leftovers from other contexts 😄 Closing here and moving to the mailing list