From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Frederic Martinsons <frederic.martinsons@gmail.com>
Cc: docs@lists.yoctoproject.org,
openembedded-core@lists.openembedded.org,
Marta Rybczynska <rybczynska@gmail.com>,
Paul Eggleton <paul.eggleton@linux.microsoft.com>,
Alex Kiernan <alex.kiernan@gmail.com>
Subject: Re: [docs] [OE-core] [PATCH] migration-guides: update 4.2 migration and release notes
Date: Thu, 6 Apr 2023 10:23:27 +0200 [thread overview]
Message-ID: <67d102c4-cb70-169d-b8ad-cb141378b7f0@bootlin.com> (raw)
In-Reply-To: <CA+cAkeoPkXN+4Z39DWewrhSL1c3GSsbadPhY-_=Rf9p-Na5u+Q@mail.gmail.com>
Hi Frederic
On 05.04.23 at 21:04, Frederic Martinsons wrote:
>
>
>
> Any more Rust changes we should mention in the migration notes?
>
>
> Maybe mention a specific procedure to update a cargo based recipe from
> scratch (i.e. a recipe that
> didn't use the cargo-update-recipe-crates inheritance):
>
> To bootstrap a cargo base recipe which have not the checksum list,
> below are
> the steps to make:
> - make the recipe inherit cargo-update-recipe-crates
> - remove all crate:// from the recipe
> - create an empty ${BPN}-crates.inc file and make your recipe
> requires it
> - execute "bitbake -c update_crates your_recipe"
> - copy paste the output of bitbake about the missing checksums in
> your ${BPN}-crates.inc
>
> The last step requires a bitbake patch to show all the missing
> checksum which I don't know
> if it will be in 4.2.
Do you mean this one?
https://git.openembedded.org/bitbake/commit/?h=2.4&id=dafa07c080e05975b6319b5adf78a9691c6b6643
It just got merged.
Thanks for the tip.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-04-06 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17531B0D0DFA1CB6.3977@lists.openembedded.org>
2023-04-05 18:40 ` [OE-core] [PATCH] migration-guides: update 4.2 migration and release notes Michael Opdenacker
2023-04-05 19:04 ` Frédéric Martinsons
2023-04-06 8:23 ` Michael Opdenacker [this message]
2023-04-06 8:52 ` [docs] " Frédéric Martinsons
2023-04-06 9:12 ` [PATCH v2] " michael.opdenacker
2023-04-06 10:12 ` [OE-core] " Richard Purdie
2023-04-06 20:53 ` Michael Opdenacker
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=67d102c4-cb70-169d-b8ad-cb141378b7f0@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=alex.kiernan@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=frederic.martinsons@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.microsoft.com \
--cc=rybczynska@gmail.com \
/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