elodin-sys
Bevy 0.17 dependency audit
We expect to run into a number of dependency issues updating to bevy 0.17. This is a good opportunity to determine what our dependency exposure is wrt bevy.
Questions:
- Which 3rd party crates do we depend on that have already updated to 0.17?
- Which 3rd party crates have not updated?
- Which vendored crates do we need to updated?
- Can any dependencies be dropped?
- ...?
We're using forked versions of big_space, bevy_editor_cam, and bevy_framepace. The forks are all by different accounts, but the upstream is https://github.com/aevyrie for all of them, and the upstream versions are more up-to-date. This is a pretty weird situation, but seems intentional. @x46085 any lore on how we got here?
This is a pretty weird situation, but seems intentional. @x46085 any lore on how we got here?
This is when I typically play archeologist in the current and previous repo (elodin/paracosm respectively), I start with looking at historical PRs that could be related, such as searching like so: https://github.com/elodin-sys/paracosm/pulls?q=is%3Apr+big_space
Git blame is also useful, made it very simple to find the commit where big_space was changed to a fork, for example: https://github.com/elodin-sys/elodin/commit/8bbb94e917aa2298b97171af1402d6362be44dfa
