docs: Add instructions for updating wasmtime
#322
Conversation
Signed-off-by: Ryan Northey <ryan@synca.io>
|
Would be helpful to document the manual changes required as a result of this bug. google/cargo-raze#451 It caused me a lot of pain |
|
yep just hitting that now 8( (#319 ) any ideas on how to fix ? |
|
@phlax Is this finished? I thought there were a few more things that you wanted to add here, but I don't recall details. |
i can have a go - its the issue of resolving duplicates - not sure exactly what to say - iirc the easiest is to diff the changed files but dont rem exactly what/where |
Signed-off-by: Ryan Northey <ryan@synca.io>
phlax
force-pushed
the
wasmtime-readme
branch
from
eb27cc7 to
471e14a
Compare
|
|
||
| Resolving this issue can be tricky as updates can generate a lot of change, but essentially | ||
| you will need to check the overall diff for any problematic files and check to see where new | ||
| dependencies have been added. |
There was a problem hiding this comment.
@PiotrSikora this feels pretty unsatisfactory but looking over the actual diffs (and checking through my/others attempts to resolve) im not clear what the process here should be
when we recently updated this - i seem to rem right at the end a penny dropping and thinking "ok, got it" but im not sure what that was now or how to describe in a way that will work given the different possibilities regenerating the file has.
is there any way we could resolve the upstream raze issue ?
| ## Install `cargo-raze` | ||
|
|
||
| ```console | ||
| $ cargo install cargo-raze --version 0.14.1. |
There was a problem hiding this comment.
| $ cargo install cargo-raze --version 0.14.1. | |
| $ cargo install cargo-raze --version 0.14.1 |
Signed-off-by: Ryan Northey ryan@synca.io