bitbake-setup steps for release

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

Hi All,

Huge thanks to everyone who has sent patches. Having multiple people
looking at this and sending them has allowed "parallel processing" that
is really moving us closer to release.

The review call agreed with the patches on master-next and that those
should merge. Not all are perfect and there will be some further tweaks
needed but they do move things closer to where we need to be.

There are some things we all thought still needed fixing before
release:

a) The update command needs to prompt y/n on overwriting bblayers.conf
or local.conf and give the users a choice. We need a way for users to
update the repos with one command, we can improve the conf file
upgrading later.

b) There should be a --no-conf-updates (better naming?) to the update
command

c) The default build path should not include the machine name. Ryan
mentioned his previous patches which have the concept of a format
string, or we have a include y/n piece in the json config. Otherwise
you can end up with multiple elements like poky_poky.

d) We need to tell the user how to change the machine/distro layer as
nobody knows about the bitbake-config-build command. Mention "bitbake-
config-build enable-fragment machine/XXX" in output when running the
tool.

e) Add a comment into toolcfg.conf to point at the command to change

f) Catch conf file configuration of MACHINE/DISTRO conflicting with a
fragment?

I'll let anyone add anything I've missed.

Thanks all, it was a really useful call and gives us an idea of what we
need to do to be able to release.

Cheers,

Richard