Marc BK
Marc BK
> I'm also seeing this behavior: it's causing my CI runs to fail. For stable installs you should always use the `--locked` option.
> > > I'm also seeing this behavior: it's causing my CI runs to fail. > > > > > > For stable installs you should always use the `--locked`...
> I've got this problem as well - maybe I'm obtuse, but is there a workaround that I missed? cargo install [email protected] --locked
I have not looked at refactoring the whole module but I refactored `PacketRef` out into a separate module here: https://github.com/andrei-ng/u-blox.rs/pull/48, maybe my comments help you a bit? Also [cargo expand](https://github.com/dtolnay/cargo-expand)...
Your plan sounds good, I expect @andrei-ng will agree but let's hear from him so we can focus the effort and avoid duplicate work. I'm very new to ublox, just...
> I am willing to do the grunt work and pull all the packet additions I have in my fork here as separate PRs for you guys to approve. Most...
> We have zero means to publish a library update as of right now, so it is the priority to unlock this. Eventually, we should have a git tag CI...
You can use the approach described here: https://opensource.axo.dev/cargo-dist/book/ci/customizing.html?highlight=build-setup.yml#customizing-build-setup To first install `musl-tools` e.g. add a step with `sudo apt-get update && sudo apt-get install musl-tools` Here's an example from one...
Any news on this? We have a use case for it where it would _just_ be perfect 😎
Interesting, thanks for the quick response. Is it something you intend to fix?