11677 2017-06-15 23:37:03 +0000 eSDK: add layer management functionality 2025-07-03 15:32:51 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain unspecified x86 Multiple NEW Medium enhancement Future 12167 1 henry.bruce unassigned bluelightning brian.avery leonardo.sandoval.gonzalez matthew.k.hansen meta.mr.watcher meta.watcher randy.macleod sgw --- --- Yes (doc changes required) oldest_to_newest 74261 0 henry.bruce 2017-06-15 23:37:03 +0000 A key part of the devtool enabled workflow is creating new recipes. Often such recipes are added to a new layer that is specific to the project they serve. It would simplify the workflow if devtool could create a layer, rather expecting the developer to do that manually or use yocto-layer command (unlikely as it is not well publicized). 74331 1 henry.bruce 2017-06-19 16:45:16 +0000 also support add/remove layers as done by 'bitbake-layers' command. This appears to work in eSDK but is not in the path (layers/build/bitbake/bin) as bitbake is deliberately hidden from user. 77310 2 brian.avery 2017-10-03 17:56:59 +0000 So, I'm not a fan of adding tons of new devtool commands for something that can be done directly by existing tools. For me, the devtool indirection just gets in the way when things go wrong. That being said, I'd like to change the title of this to something like "Support bitbake-layers in the esdk". Right now, we cannot make a new layer from the esdk. If I do a devtool modify, followed by a devtool finish, I need a layer for the changes to land in. I can (right now) run yocto-layer directly from the esdk since I know where it lives, but it is not on the path by default. bitbake-layers (which is likely to be the only layer creation in the future Bug 12167) cannot be run directly w/o some additional work. This comment proposes to change the title to "Support bitbake-layers in the esdk". and to make botbake-layers be on the path for an esdk. 77361 3 bluelightning 2017-10-04 21:10:41 +0000 I'm renaming this bug to more accurately represent what we want to do. I think at the same time I think ideally we shouldn't be exporting something with "bitbake" in the name, so we might take this opportunity to rename bitbake-layers to bblayers or layertool or something like that. 77883 4 rebecca.swee.fun.chang 2017-10-31 06:24:31 +0000 Just jotting down my assessment on this bug so I could remind myself when I start to work on it. Before we could start adding layer management functionality to eSDK. There are dependencies to resolve. 1. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12167 Removing yocto-layer and use bitbake-layers. 2. Remove yocto-layer support from eSDK. 3. Rename bitbake-layers to bblayers or layertool or something like that. Required decision to fix the command naming convention. I would vote +1 for layertool. 80090 5 leonardo.sandoval.gonzalez 2018-04-04 07:33:15 +0000 target milestone 2.99? does future now means 2.99? 80094 6 bluelightning 2018-04-04 13:40:31 +0000 See here: https://www.mail-archive.com/linux-yocto@yoctoproject.org/msg06283.html 95856 7 randy.macleod 2023-06-29 16:38:25 +0000 Still worth doing when we have the people available. -- YP bug review. 102399 8 randy.macleod 2025-07-03 15:32:51 +0000 Still worth doing when we have the people available. -- YP bug review.