-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In regards to automatic update patch generation this actually is pretty
useful. I think I'll throw an extra patch on top to integrate this
suggestion.
- --
With best regards
Jasper Orschulko
DevOps Engineer
Tel. +49 30 58 58 14 265
Fax +49 30 58
.org
> > Cc: mar...@mko.dev; daniel.baumg...@iris-sensing.com;
> > bitbake-de...@lists.openembedded.org; Jasper Orschulko
> >
> > Subject: [oe-core][PATCH v5 1/2] repo: Add recipe for 2.17.3
> >
> > From: Jasper Orschulko
> >
> > Add a recipe for re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Jose,
> I think we can replace the patch 0001-Set-REPO_REV-to-v2.17.3.patch
> with a post function
> and with it we can reuse the SRCREV of the recipe. Something like:
>
> do_fix_rev(){
> sed -i "s/REPO_REV = 'stable'/REPO_REV = '${SRCREV}'"
ng.com;
> bitbake-de...@lists.openembedded.org; Jasper Orschulko
>
> Subject: [oe-core][PATCH v5 1/2] repo: Add recipe for 2.17.3
>
> From: Jasper Orschulko
>
> Add a recipe for repo 2.17.3, prerequisite for the repo fetcher.
>
> Signed-off-by: Jasper Orschulko
&
Jasper Orschulko via lists.openembedded.org escreveu no dia quinta, 11/11/2021
à(s) 10:21:
> From: Jasper Orschulko
>
> Add a recipe for repo 2.17.3, prerequisite for the repo fetcher.
>
> Signed-off-by: Jasper Orschulko
> ---
> meta/conf/distro/include/maintainers.inc | 1 +
> .../0001-
From: Jasper Orschulko
Add a recipe for repo 2.17.3, prerequisite for the repo fetcher.
Signed-off-by: Jasper Orschulko
---
meta/conf/distro/include/maintainers.inc | 1 +
.../0001-Set-REPO_REV-to-v2.17.3.patch| 35 +++
.../repo/repo/0001-python3-shebang.patch
