7792 2015-05-19 15:39:06 +0000 Layer compatible branches expansion (parse LAYERSERIES_COMPAT) 2026-02-12 16:21:57 +0000 1 1 6 Yocto Project Subprojects Layer Index Layer Index unspecified All Multiple NEW Medium enhancement Future 8008 1 bluelightning unassigned belen.barros.pena brian.avery jose.perez.carranza konrad.scherer randy.macleod tim.orling --- --- No (bug/feature does not impact docs) oldest_to_newest 51148 0 bluelightning 2015-05-19 15:39:06 +0000 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 80177 1 bluelightning 2018-04-09 22:28:50 +0000 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. 97734 2 tim.orling 2024-01-04 17:13:28 +0000 At least the ability to edit the 'actual_branch' is now available. There is currently no handling of the LAYERSERIES_COMPAT variable, however. 104268 3 tim.orling 2026-02-12 16:21:57 +0000 Still valid.