13080 2018-12-12 19:29:28 +0000 devtool: handle user modifying local files next to recipe 2026-08-13 15:25:35 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 5.99 x86 Multiple NEW Medium+ enhancement 6.99 1 bluelightning unassigned randy.macleod ross.burton --- --- Don't know oldest_to_newest 82483 0 bluelightning 2018-12-12 19:29:28 +0000 devtool modify/upgrade set up an oe-local-files subdirectory of the source tree to provide a place to make changes/additions to non-patch local files, however it is possible that the user will not realise this and attempt to modify files next to the recipe - in the case of devtool modify these would be the original files next to the recipe, in the case of devtool upgrade they would be in the workspace next to the upgraded recipe file. If the user does modify these files then nothing will actually happen - the files in oe-local-files will be used in preference. If practical we should at least show a warning if those files are newer than the ones in oe-local-files; bonus if it ignores this if the checksum has not changed from the original. The practical question though would be when we would do this checking and warning; presumably it would have to be triggered within the metadata or bitbake to be useful. (See also bug 13079 - part of the reason why users might miss this is it's currently undocumented.) 96873 1 randy.macleod 2023-10-24 14:24:34 +0000 Bulk move from 4.99 or 0.00 to 5.99