Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: update dependencies and emit checksums #75

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

jaskij
Copy link

@jaskij jaskij commented Apr 24, 2024

  • 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
Copy link
Author

jaskij commented Apr 24, 2024

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
Copy link
Author

jaskij commented Apr 25, 2024

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

@Finomnis
Copy link

Finomnis commented Apr 25, 2024

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
Copy link
Author

jaskij commented Apr 26, 2024

@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

@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
Copy link
Author

jaskij commented Apr 26, 2024

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
Contributor

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

@jaskij
Copy link
Author

jaskij commented Jan 2, 2025

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
Copy link

Finomnis commented Jan 2, 2025

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
Copy link
Author

jaskij commented Jan 2, 2025

@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