Bug 7792

Summary: Layer compatible branches expansion (parse LAYERSERIES_COMPAT)
Product: [Yocto Project Subprojects] Layer Index Reporter: Paul Eggleton <bluelightning>
Component: Layer IndexAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: Medium CC: belen.barros.pena, brian.avery, jose.perez.carranza, konrad.scherer, randy.macleod, tim.orling
Version: unspecified   
Target Milestone: Future   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on: 8008    
Bug Blocks:    

Description Paul Eggleton 2015-05-19 15:39:06 UTC 
At the moment we rely on individual layers having a branch that matches the name of the release branch (e.g. fido) for it to show up as being compatible with a particular release; however that doesn't always match reality. It would be useful if we could do a couple of things:

1) Have the layer show up as compatible with other branches even if there isn't an explicit branch for that release. We'd need to have some idea that it's compatible with the branch - perhaps for recent releases we do a test parse with the master branch of the layer and match that to the release if it succeeds. (We'd want to perhaps display that we'd done that.)

2) Possibly show the other compatible branches for a layer if they can be shown without disturbing the design too much
Comment 1 Paul Eggleton 2018-04-09 22:28:50 UTC 
I think this is now much more easily achievable with the advent of LAYERSERIES_COMPAT:

http://lists.openembedded.org/pipermail/openembedded-architecture/2018-April/000722.html

Presumably we would have to dynamically create layerbranch records to represent what's in LAYERSERIES_COMPAT_xxxx for a particular branch.
Comment 2 Tim Orling 2024-01-04 17:13:28 UTC 
At least the ability to edit the 'actual_branch' is now available. There is currently no handling of the LAYERSERIES_COMPAT variable, however.
Comment 3 Tim Orling 2026-02-12 16:21:57 UTC 
Still valid.