On Wed, 5 Apr 2023 at 20:40, Michael Opdenacker <
michael.opdenac...@bootlin.com> wrote:
> Greetings,
>
> I copied the OE-core mailing list to get the attention of contributors.
> If you want your new features to be featured in the release and
> migration notes for 4.2, it's time to speak!
>
> What I wrote so far is a very early draft meant to help you detect
> what's missing and correct what I've written so far.
>
> See my questions and comments below...
>
> On 05.04.23 at 19:46, Michael Opdenacker via lists.openembedded.org wrote:
> > diff --git a/documentation/migration-guides/migration-4.2.rst
> b/documentation/migration-guides/migration-4.2.rst
> > index 1339411b3e..3b04e072cb 100644
> > ...
> > +Rust: mandatory checksums for crates
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +This release now supports checksums for Rust crates and make
> > +them mandatory for each crate in a recipe. See
> :yocto_git:`python3_bcrypt recipe changes
> >
> +</poky/commit/?h=mickledore&id=0dcb5ab3462fdaaf1646b05a00c7150eea711a9a>`
> > +for example.
> > +
> > +The ``cargo-update-recipe-crates`` utility
> > +:yocto_git:`has been extended
> </poky/commit/?h=mickledore&id=eef7fbea2c5bf59369390be4d5efa915591b7b22>`
> > +to include such checksums.
>
>
> 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.
> > +
> > +- Rust improvements:
> > +
> > + - This release adds Cargo support on the target, and includes
> > + automated QA tests for this functionality.
> > +
> > + - It also supports checksums for Rust crates and makes
> > + them mandatory for each crate in a recipe.
>
>
> More Rust changes we should highlight?
>
This one seems redundant with the previously mentioned rust changes, isn't
it ?
Nevertheless, I'd maybe add a line about the fact that now we can develop
rust project which contains "private" crate (i.e. crates that would be
hosted
in a git repository instead of crates.io registry), and by develop, it
means we
can of course build such a package but perform devtool operation on it (at
least devtool modify and devtool deploy-target)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#179748):
https://lists.openembedded.org/g/openembedded-core/message/179748
Mute This Topic: https://lists.openembedded.org/mt/98088099/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
