Skip to content

WIP: update dependencies and emit checksums#75

Open
jaskij wants to merge 8 commits into
meta-rust:masterfrom
jaskij:master
Open

WIP: update dependencies and emit checksums#75
jaskij wants to merge 8 commits into
meta-rust:masterfrom
jaskij:master

Conversation

@jaskij

@jaskij jaskij commented Apr 24, 2024

Copy link
Copy Markdown
  • update the dependencies to latest versions
  • also merged emit inline checksum #73 because I needed a single version that does it all
  • MSRV 1.75

@jaskij

jaskij commented Apr 24, 2024

Copy link
Copy Markdown
Author

I made this fork because I needed latest dependency versions in one place with @ensc's inline checksums from #73. Not entirely sure if it is intended to be merged, or just for others to use before master gets updated.

@jaskij

jaskij commented Apr 25, 2024

Copy link
Copy Markdown
Author

I had to remove inline checksums because as it turns out they don't work with Kirkstone

@Finomnis

Finomnis commented Apr 25, 2024

Copy link
Copy Markdown

I had to remove inline checksums because as it turns out they don't work with Kirkstone

But it doesn't work on newer versions without them. Any way this could become a cli flag? With enabled by default, because it's required on all newer versions?

@jaskij

jaskij commented Apr 26, 2024

Copy link
Copy Markdown
Author

@Finomnis good idea, I mostly treated this as a semi-private WIP, but yeah, the checksums should be default, but optional. Done.

The commit history is a mess though.

@Finomnis

Copy link
Copy Markdown

@Finomnis good idea, I mostly treated this as a semi-private WIP, but yeah, the checksums should be default, but optional. Done.

The commit history is a mess though.

That's fine, I guess :D that's what squash merge is for :P

@jaskij

jaskij commented Apr 26, 2024

Copy link
Copy Markdown
Author

For what it's worth, while I'm not doing much testing, I am dogfooding this fork, and so far it's 2/2 working, including git dependencies and path dependencies within repo. No submodules though.

@paolobarbolini

Copy link
Copy Markdown
Contributor

Maybe cargo-update-recipe-crates (see #83) would be a better solution for newer Yocto versions?

@jaskij

jaskij commented Jan 2, 2025

Copy link
Copy Markdown
Author

FWIW, I have just rebased it on top of master, but that's only to get a consistent state for my work on rewriting the thing from scratch.

@Finomnis

Finomnis commented Jan 2, 2025

Copy link
Copy Markdown

I also switched to Yocto's built-in mechanism. In my opinion think this crate should be deprecated, as it tends to lead new users down the wrong path of how to integrate Rust into Yocto.

See #83.

@jaskij

jaskij commented Jan 2, 2025

Copy link
Copy Markdown
Author

@Finomnis totally fair, but I do need it working unless I can move our devices off of Kirkstone, and I know there are others who use pre-Scarthgarp versions of Yocto.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants