[bitbake-devel] devtool hardcodes using 'git' patchtool which causes errors
adrian.ambrozewicz at linux.intel.com
Wed Jan 22 08:49:11 UTC 2020
I see. However - this looks like quite a minefield :)
W dniu 1/21/2020 o 11:49, Alexander Kanavin pisze:
> I am not entirely sure about this, but I believe devtool is using git to
> keep track of patches when modifying or upgrading (e.g. adding,
> modifying or rebasing custom recipe patches), so using quilt may not be
> an option. Fixing the scenarios that go wrong for you is probably a
> better path.
> On Tue, 21 Jan 2020 at 10:44, Adrian Ambrożewicz
> <adrian.ambrozewicz at linux.intel.com
> <mailto:adrian.ambrozewicz at linux.intel.com>> wrote:
> In poky sources i can see that default PATCHTOOL used is 'quilt'
> and it works flawlessly. Devtool however still defaults to legacy 'git'
> PATCHTOOL, as specified here:
> > f.write('PATCHTOOL = "git"\n')
> I've tried to debug the problem but I'm not very familiar with Bitbake
> code, so I wonder if we could default to 'quilt' for devtool as well?
> 'git' PATCHER doesn't work well when he have nested WORKDIR and
> striplevel used. 'bitbake -c patch [pkg]' works fine, but 'devtool
> modify [pkg]' fails with weird behavior. For example - new files
> by patches are created in wrong location (WORKDIR instead of nested
> directory) and package doesn't compile until manually fixed.
> bitbake-devel mailing list
> bitbake-devel at lists.openembedded.org
> <mailto:bitbake-devel at lists.openembedded.org>
More information about the bitbake-devel