Re: [poky] [PATCH] meta-poky/conf: bblayers.conf.sample: move meta-yocto repos out of oe-core

["Antonin Godard" <antonin.godard@bootlin.com>]

On Tue Oct 28, 2025 at 12:49 PM CET, Alexander Kanavin via lists.yoctoproject.org wrote:
> On Tue, 28 Oct 2025 at 11:50, Antonin Godard via
> lists.yoctoproject.org
> <antonin.godard=bootlin.com@lists.yoctoproject.org> wrote:
>> I'm also in the process of creating a document in yocto-docs that
>> describes how to build the Poky reference distro without bitbake-setup,
>> and that uses this file to setup layers. So this layout will also be
>> reflected in the documentation.
>
> I assume this will be presented as the 'backup/historical option',
> after the bitbake-setup flow, which will be the primary choice?

Yes

>>  BBLAYERS ?= " \
>>    ##OEROOT##/meta \
>> -  ##OEROOT##/meta-poky \
>> -  ##OEROOT##/meta-yocto-bsp \
>> +  ##OEROOT##/../meta-yocto/meta-poky \
>> +  ##OEROOT##/../meta-yocto/meta-yocto-bsp \
>
> There is a complication here. Integrated poky repository is not
> deprecated (yet), a lot of people are using it (still), and when it's
> assembled with combo-layer, then this file needs to be reverted to how
> it was. I'm not sure if this is easily doable, but without that tweak,
> this patch cannot go in, until integrated poky repo is truly obsoleted
> and is no longer receiving new commits.
>
> I suspect everything would have to be done in lockstep, and at the same time:
> - obsolete poky repo
> - merge this tweak
> - merge documentation changes that explain how to assemble poky
> without cloning the poky repo.

Thanks for the feedback.

I haven't tested this, but maybe in the meantime we can have a temporary
template to set this up? Something like:

templates
├── default
│   ├── bblayers.conf.sample
│   ├── conf-notes.txt
│   ├── conf-summary.txt
│   ├── local.conf.sample
│   ├── local.conf.sample.extended
│   └── site.conf.sample
└── no-poky-repo
    ├── bblayers.conf.sample
    ├── conf-notes.txt -> ../default/conf-notes.txt
    ├── conf-summary.txt -> ../default/conf-summary.txt
    ├── local.conf.sample -> ../default/local.conf.sample
    ├── local.conf.sample.extended -> ../default/local.conf.sample.extended
    └── site.conf.sample -> ../default/site.conf.sample

With the only difference in no-poky-repo being the layers layout, compared to
the default one.

Then later we remove this, and the docs can be updated easily.

The point is that the sooner we have the documentation for either bitbake-setup
or manual poky setup, the sooner we can send a docs link to people asking how to
switch to the new setup (one way or the other).

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com