Re: [PATCH v2 0/4] Make adjust_git work in both worlds

[Uladzimir Bely <ubely@ilbers.de>]

In the email from воскресенье, 15 августа 2021 г. 22:02:25 +03 user Jan Kiszka 
wrote:
> On 13.08.21 14:40, Uladzimir Bely wrote:
> > When I previously looked at patch.bbclass, I noted, that we don't use it
> > completely.
> > 
> > There are some patch_task_patch_prefunc() and patch_task_postfunc() here
> > that are used in OE when PATCHTOOL='git'. But in our case they are never
> > run due to not using PATCH_COMMIT_FUNCTIONS in isar.
> > 
> > I suppose (but can't be completely sure without deep look to OE) that
> > prefunc may fix this 'patch is allready applied' issue in OE.
> 
> If you can still reproduce the issue, just set PATCH_COMMIT_FUNCTIONS=1
> to check if it has any impact.
> 
> Browsing poky and OE-core, I only find devtool setting this var. But
> both aren't using git as patch tool anyway, a downstream layer/recipe
> needs to requests that.
> 
> Jan

Yes, I also tried this way.

Actually, enabling PATCH_COMMIT_FUNCTIONS also forces to make some more 
changes in patch.bbclass (like sys.path.insert for OE lib path) that makes the 
difference increase.

Anyway, even if this set to "1", the problem of patch reapply is still here - 
custom patch is going to be applied despite it was already done on previous 
build. So, reset to SRC_REV is still required.

-- 
Uladzimir Bely
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov