[bitbake-devel] devtool hardcodes using 'git' patchtool which causes errors

[Alexander Kanavin]

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.

Alex

On Tue, 21 Jan 2020 at 10:44, Adrian Ambrożewicz <
adrian.ambrozewicz at linux.intel.com> wrote:

> In poky sources i can see that default PATCHTOOL used is 'quilt'
> (
> https://github.com/openembedded/openembedded-core/blob/master/meta/conf/bitbake.conf)
>
> and it works flawlessly. Devtool however still defaults to legacy 'git'
> PATCHTOOL, as specified here:
>
> http://git.yoctoproject.org/cgit.cgi/poky/plain/scripts/lib/devtool/standard.py
>   > f.write('PATCHTOOL = "git"\n')
>
> Request:
> 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?
>
> Rationale:
> '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 created
> by patches are created in wrong location (WORKDIR instead of nested
> directory) and package doesn't compile until manually fixed.
>
> Regards,
> Adrian
> --
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20200121/0be97396/attachment-0001.html>