From: tim.orling@konsulko.com
To: openembedded-core@lists.openembedded.org
Cc: bluelightning@bluelightning.org
Subject: [RFC PATCH 0/3] Implement RECIPE_UPDATE_EXTRA_TASKS
Date: Sun, 2 Jun 2024 14:00:37 -0700 [thread overview]
Message-ID: <cover.1717361301.git.tim.orling@konsulko.com> (raw)
From: Tim Orling <tim.orling@konsulko.com>
Whenever a recipe which inherits cargo-update-recipe-crates is upgraded with
devtool (such as with the Auto Upgrade Helper) we frequently see failures.
If the upstream Cargo.toml or Cargo.lock has been changed, the corresponding
<recipe_name>-crates.inc needs to be updated. This is done by running the
"bitbake -c update_crates <recipe_name>" task, but this has until now been
a manual operation.
Add a new variable RECIPE_UPDATE_EXTRA_TASKS which is a string delimited
list of tasks to be run during the upgrade() method of
meta/lib/devtool/upgrade.py.
To solve the problem described above, the solution is for all recipes which
inherit cargo-update-recipe-crates to add the "do_update_crates" task to
the RECIPE_UPDATE_EXTRA_TASKS variable. Add this to the bbclass.
Add test case based on the guessing-game source we currently use for the
maturin runtime test cases, based on https://www.maturin.rs/tutorial.
This oe-selftest case checks for both the change in the recipe file and
the recipe -crates.inc file.
This will rely on a new "guessing-game" git repository to be added to
git.yoctoproject.org/guessing-game (currently hosted on GitHub for the
purposes of this RFC).
Currently, update_crates is the only task known to the author to fall into
this RECIPE_UPDATE_EXTRA_TASKS use case. If anyone can think of other use
cases that can also be added (and tested!), please let me know.
Two obvious use cases that would be nice to add with changes in oe-core are:
(1) some kind of "go-mod://" update class to use a similar <recipe>-go-mods.inc
(2) some kind of rework of the "npm://" fetcher to use <recipe>-npm-mods.inc
But both of those are out of scope for this proposal.
The _run_recipe_update_extra_tasks() method added to lib/devtool/upgrade.py
is functional, but could probably use some more guards and checks. Ideas for
improvements are welcome, hence the RFC.
An attempt at documenting the new variable has been added to ref-manual,
but if anyone has some ideas for better clarification, input is welcome.
The following changes since commit af6d28d2b0abdfcfa70edcc95abd99a3c1a64ac8:
sanity: Check if tar is gnutar (2024-05-31 16:58:36 +0100)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib timo/RECIPE_UPDATE_EXTRA_TASKS
https://git.yoctoproject.org/poky-contrib/log/?h=timo/RECIPE_UPDATE_EXTRA_TASKS
Tim Orling (5):
devtool upgrade: enable RECIPE_UPDATE_EXTRA_TASKS
cargo-update-recipe-crates: add RECIPE_UPDATE_EXTRA_TASKS
ref-manual: add RECIPE_UPDATE_EXTRA_TASKS variable
meta-selftest: add python3-guessing-game
oe-selftest: add RECIPE_UPDATE_EXTRA_TASKS test
documentation/ref-manual/variables.rst | 7 ++
.../python/python3-guessing-game-crates.inc | 82 +++++++++++++++++
.../python3-guessing-game-crates.inc.upgraded | 88 +++++++++++++++++++
.../python/python3-guessing-game_git.bb | 19 ++++
.../python3-guessing-game_git.bb.upgraded | 19 ++++
.../cargo-update-recipe-crates.bbclass | 2 +
meta/lib/oeqa/selftest/cases/devtool.py | 46 ++++++++++
scripts/lib/devtool/upgrade.py | 12 +++
8 files changed, 275 insertions(+)
create mode 100644 meta-selftest/recipes-devtools/python/python3-guessing-game-crates.inc
create mode 100644 meta-selftest/recipes-devtools/python/python3-guessing-game-crates.inc.upgraded
create mode 100644 meta-selftest/recipes-devtools/python/python3-guessing-game_git.bb
create mode 100644 meta-selftest/recipes-devtools/python/python3-guessing-game_git.bb.upgraded
--
2.45.2
next reply other threads:[~2024-06-02 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 21:00 tim.orling [this message]
2024-06-02 21:00 ` [RFC PATCH 1/5] devtool upgrade: enable RECIPE_UPDATE_EXTRA_TASKS tim.orling
2024-06-04 6:42 ` [OE-core] " Richard Purdie
2024-06-02 21:00 ` [RFC PATCH 2/5] cargo-update-recipe-crates: add RECIPE_UPDATE_EXTRA_TASKS tim.orling
2024-06-02 21:00 ` [RFC PATCH 3/5] ref-manual: add RECIPE_UPDATE_EXTRA_TASKS variable tim.orling
2024-06-02 21:00 ` [RFC PATCH 4/5] meta-selftest: add python3-guessing-game tim.orling
2024-06-02 21:00 ` [RFC PATCH 5/5] oe-selftest: add RECIPE_UPDATE_EXTRA_TASKS test tim.orling
2024-06-03 9:09 ` [OE-core] [RFC PATCH 0/3] Implement RECIPE_UPDATE_EXTRA_TASKS Alexander Kanavin
2024-06-03 15:14 ` Tim Orling
2024-06-03 14:08 ` Richard Purdie
2024-06-03 15:13 ` Tim Orling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1717361301.git.tim.orling@konsulko.com \
--to=tim.orling@konsulko.com \
--cc=bluelightning@bluelightning.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox