dkebler

If I understand the custom-image script is run as a chroot after the image is built. So didn't see anything specifically in the docs but can I ONLY run (from compile script) the custom image script on an already already built image (in /output/images)? Along the same lines can I chroot at any time to the image via the compile script? I should mention that I am using the docker container build for arm on my amd machine. (i.e. ./compile.sh docker.... )

I wanted to build the cli version but didn't see an obvious way to do that with conf variables and the docs don't illuminate that choice. so I tried BUILD_MINIMAL=no BUILD_DESKTOP=no and that seems to do force the cli version. Just suggesting that this might be easier to grok if the variable was say BUILD_TYPE=(desktop|cli|minimal|custom) with maybe default cli where custom might be a rootfs that is custom (like one I put together) and thus doesn't need to be reconstructed from the custom-image script. Maybe setting custom then RELEASE could hold the path to the tarball? If that seems better maybe I can try making a pr? BTW this is not necessarily a beginner topic but didn't see a category for just generic building discussion.