Bug 12678

Summary:	devtool finish ignoring PREFERRED_PROVIDER_virtual/kernel
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Andrea Adami <andrea.adami>
Component:	devtools / tool chain	Assignee:	Chris Laplante <chris.laplante>
Status:	IN PROGRESS IMPLEMENTATION ---	QA Contact:
Severity:	minor
Priority:	Medium	CC:	chris.laplante, meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie, tim.orling
Version:	2.5
Target Milestone:	6.99
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

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.