12678 2018-04-12 06:54:35 +0000 devtool finish ignoring PREFERRED_PROVIDER_virtual/kernel 2026-04-23 15:30:02 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 2.5 x86 Multiple IN PROGRESS IMPLEMENTATION Medium minor 6.99 1 andrea.adami chris.laplante chris.laplante meta.mr.watcher meta.watcher randy.macleod richard.purdie tim.orling --- --- Don't know oldest_to_newest 80208 0 andrea.adami 2018-04-12 06:54:35 +0000 Being the syntax is: $ devtool modify <recipename> I have noticed that while it is possible to do: $ devtool modify virtual/kernel you must then do i.e.: $ devtool finish --force-patch-refresh linux-handheld /my/layer_path otherwise you get an ERROR: No recipe named 'virtual/kernel' in your workspace Cheers Andrea 81414 1 bluelightning 2018-08-23 04:10:10 +0000 Correct, it de-references virtual/kernel (or any other PROVIDES) just once, and tells you so. I'd not want to do that on every invocation since it means loading the recipe cache, but I guess we could probably get away with caching the PROVIDES for recipes in the workspace somewhere so that we could accept it. 96704 2 chris.laplante 2023-10-13 14:54:28 +0000 I have a working implementation that caches the original name used in the call to 'devtool modify', allowing lookup by subsequent calls to 'devtool', similar to what Paul described below. Will work on polishing it and adding selftests, then will submit it. 105236 3 randy.macleod 2026-04-23 15:23:15 +0000 Chris any news ? 105238 4 chris.laplante 2026-04-23 15:30:02 +0000 Wow, can't believe it's been three years :(. I will try to find some time in the coming weeks to get this upstream, or at the very least post what I have here so someone can pick up where I left off.