Question: LIB_TAG sunxi-4.20 about bitbox-base HOT 6 CLOSED

There's nothing stopping you to just remove the LIB_TAG, this should not break something systemically. We pinned the tag to avoid having a moving target and pulling in new code from the master branch all the time. We did not test the master branch build for about a month now.

Any special reason to build directly from master, like a specific improvement or feature?

from bitbox-base.

Yes, this commit: armbian/build@5b9d211#diff-3254677a7917c6c01f55212f86c57fbf

This will dramatically speed up updating the image. Because right now, each build create a new image which waste space and invalidate some cached stuff.

from bitbox-base.

Oh actually sunxi-5.0 released with this commit, can we update to it?

from bitbox-base.

Let's test it locally to see if it introduces any os issues, and then we can bump the fixed version to sunxi-5.0. I can do that next week, let me know if you have earlier results.

from bitbox-base.

ok, I am trying on my own fork. I am getting trouble in the customize image to download the docker images :(
Running a docker inside a docker which run on qemu inside a chroot, I don't manage to run an additional docker inside to pull the images in the customize script :(

from bitbox-base.

Closing this issue as we're currently building from master branch without any issues. Need to lock in the release / commit when going from DEV to TEST/PROD mode, though.

from bitbox-base.