Bug 12313 - recipetool needs a place to put dummy recipes / bbappends
Summary: recipetool needs a place to put dummy recipes / bbappends
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 6.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-11-06 20:31 UTC by Paul Eggleton
Modified: 2026-08-13 15:10 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2017-11-06 20:31:31 UTC
Since the refactoring I did in 2.4 for devtool/recipetool fetching new source, we actually need to create a "dummy" recipe in order to be able to run do_fetch/do_unpack/do_patch with the desired SRC_URI, then run the tasks, then delete the recipe. To do this we look through BBFILES and pick a place to put the recipe, favouring the workspace layer if it's present - but it may not be if the user is running recipetool and devtool has never been run. 

This current method is a kludge. We could really use a place to put these dummy recipes temporarily without potentially writing things into a random layer in the user's configuration. Of course we could add a layer on the fly, but that would trigger a full reparse of the metadata which I think would be worse.
Comment 1 Randy MacLeod 2023-10-24 14:24:41 UTC
Bulk move from 4.99 or 0.00 to 5.99