Lukas Piatkowski 505d2e8a63 eden/scm: move third-party facebook crates dependencies to a separate folder ... Summary: Having fbsource's thrid-party crates in a separate folder will make it easier to provide a different manifest for the third-party crates for OSS builds. In order to not trigger any network calls during internal FB builds you cannot define dependencies with "git" urls. Even if they are being patched up in the same manifest Cargo will still make a call to github. That is why internall the Cargo.toml files in third-party folder will contain dependency definitions that will use "path" dependencies only. In the next diff a separate set of Cargo.toml files will be provided inside `fbcode/eden/oss` that ShipIt will replace for GitHub with the proper "git" url dependencies. Note: Why even bother with "git" and "patch" section and not use only "path" dependencies? In OSS eden builds depending on other project - like fbthrift or rust-shed. They use regular "git" dependencies. So if you try to compile Eden that uses "path" dependencies with fbthrift/rust-shed that uses "git" dependencies you will get errors from Cargo saying that e.g. rust-shed's fbthrift_ext depends on "fbthrift" (from git), but the structure X implements trait Y from "fbthrift" (from path) which is not the same as trait Y from "fbthrift" (from git). Reviewed By: quark-zju Differential Revision: D22335430 fbshipit-source-id: 9b73f4f0bc09fa79b02488dc9b4640b97f90683c		2020-07-02 03:35:02 -07:00
..
src	suggest graceful restart in hg status / old edenfs warnings	2020-04-13 16:25:58 -07:00
Cargo.toml	eden/scm: move third-party facebook crates dependencies to a separate folder	2020-07-02 03:35:02 -07:00