On Fri, Apr 19, 2024 at 2:16 PM Rasmus Villemoes via lists.openembedded.org <[email protected]> wrote:
> On 19/04/2024 23.00, Alexander Kanavin wrote: > > This was already proposed, and rejected. > > https://lists.openembedded.org/g/openembedded-core/topic/104753355 > > > > You need to fix the metadata that refers to the old name. > > So, how can a layer then be compatible with both nanbield and scarthgap? > Could this perhaps be applied just to the scarthgap branch, but not master? Ask yourself why you are choosing one branch to be compatible with multiple releases? And then have your push scripts push to a “nanbield” branch and a “scarthgap” branch. This means the Layer Index will also automatically know about your compatibility. This means any traditional Yocto project user will have zero questions about which of your branches to choose. Multiple LAYERSERIES_COMPAT is not really intent. It’s also often not accurate (layers with addpylib are not actually compatible with dunfell). Branches are cheap. Use them as intended. > > Rasmus > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#198566): https://lists.openembedded.org/g/openembedded-core/message/198566 Mute This Topic: https://lists.openembedded.org/mt/105625834/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
