Re: [Openembedded-architecture] [RFC PATCH] bitbake-setup: add the proof of concept implementation

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2024-05-02 at 12:57 +0200, Alexander Kanavin via lists.openembedded.org wrote:
> From: Alexander Kanavin <alex@linutronix.de>
> 
> For the rationale and design guidelines please see this message:
> https://lists.openembedded.org/g/openembedded-architecture/message/1913
> 
> Left out for now but will be done later:
> - config fragment support
> - tests
> - documentation
> - official configuration repository

I finally got around to looking at bitbake-setup, sorry about the
delay. For some reason I've been struggling to want to start thinking
about this!

My initial impressions are really good, I think it is a start down the
right path for what we need. I've noted down my thoughts as they came
to me:

From the init command, it isn't clear what build.sh is for. I think it
should also mention the traditional build env file too, make it clear
where that is.

I struggled to find the --build-dir option to init, I tried to specify
a direction as the next parameter but that has to be named.

For the cloning of repos, I wondered if we should have some config file
in HOME with a pointer to a central downloads/clone cache? The
autobuilder will certainly need something like that. Whether we could
use a common cache with DL_DIR remains to be seen too.

I'm not sure I like the build config being moved out the way when
updating. The tmpdir "ABI" and conf file versioning should protect us
from the worst problems?

Also, once you're "in" a build environment, can we can bitbake-setup
without parameters, i.e "bitbake-setup status" and "bitbake-setup
update"? Effectively that means teaching init-build-env about the
environment it is in so that bitbake-setup can then read the right
config from the env.

For demo purposes it might help if we could add a "poky-ng" config,
which would be poky, but built using the config from the individual
bitbake/core/meta-yocto/docs components. That shouldn't be too hard to
add?

I'll be experimenting a bit more but I wanted to give some feedback now
I've taken a look.

Cheers,

Richard