Dependencies update

[MagaTailor]

Hi, It seems updating wayland dependencies might be required to work around this issue.

The versions from Cargo.toml are affected whereas master seems to compile cleanly on ARM.

[Vinatorul]

Thank you! I am going to make an update in few minutes.

[MagaTailor]

Thx, once wayland compiles it'll become clear if other crates are still not fixed.

-original message- Subject: Re: [minesweeper-rs] Dependencies update (#43) From: Alexander Kuvaev notifications@github.com Date: 05.01.2016 12:24

Thank you! I am going to make an update in few minutes.

---

Reply to this email directly or view it on GitHub: https://github.com/Vinatorul/minesweeper-rs/issues/43#issuecomment-168975926

[MagaTailor]

Thx; is there a tool to do that recursively?

[Vinatorul]

@petevine what do you mean under recursively? I've checked versions on crates.io then used cargo update. There is cargo oudated, but I fogot to use that (:

[MagaTailor]

Recursively meaning if you update one dependency that depends on other updated crates, they would get updated too :)

For some "*" dependencies, cargo update can lead to a broken result.

[Vinatorul]

Recursively meaning if you update one dependency that depends on other updated crates, they would get updated too :)

As I know cargo works so (check diff of my Cargo.lock file from the last pull request).

For some "*" dependencies, cargo update can lead to a broken result.

I think this is rather rare for libs with >100 downloads. Wildcards nice for fast developing, but not for release, and I think anyone who will see them in Cargo.toml - will make a PR to fix it.

[MagaTailor]

One last nag - wayland-client required fixing on ARM so it needs to be bumped to 0.5.8 again.

EDIT You had better wait until I actually manage to build minesweeper again. There's still at least freetype-rs and glutin to fix.

[MagaTailor]

After bumping glutin to 0.5.8 and a cargo update, it compiles again.