-
Notifications
You must be signed in to change notification settings - Fork 62
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
base: master
Are you sure you want to change the base?
Conversation
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? |
@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 |
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. |
Maybe |
FWIW, I have just rebased it on top of |
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. |
@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. |
also merged emit inline checksum #73 because I needed a single version that does it all