Bug 12678 - devtool finish ignoring PREFERRED_PROVIDER_virtual/kernel
Summary: devtool finish ignoring PREFERRED_PROVIDER_virtual/kernel
Status: IN PROGRESS IMPLEMENTATION
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.5
Hardware: x86 Multiple
: Medium minor
Target Milestone: 6.99
Assignee: Chris Laplante
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-04-12 06:54 UTC by Andrea Adami
Modified: 2026-04-23 15:30 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea Adami 2018-04-12 06:54:35 UTC 
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
Comment 1 Paul Eggleton 2018-08-23 04:10:10 UTC 
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.
Comment 2 Chris Laplante 2023-10-13 14:54:28 UTC 
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.
Comment 3 Randy MacLeod 2026-04-23 15:23:15 UTC 
Chris any news ?
Comment 4 Chris Laplante 2026-04-23 15:30:02 UTC 
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.