Please add selective syncing about panamax

[k3d3]

The big trouble with such a feature is, for any crate, you also have to discover and grab all of its dependencies. Having the user manually specify these dependencies wouldn't be a good UX, and otherwise every crate that gets downloaded would need to be extracted, read its Cargo.toml dependencies, and then recursively download them. Then you have to decide which versions of the dependent crates get downloaded; do you download them all, or just the current latest version (which might break on upgrades)?

The nice thing about using a vendor directory is that cargo effectively handles the above for you, at least to some extent.

With all that said, I'm definitely not against such a feature existing in Panamax, however I don't have the time to work on it. I'd probably accept a PR from someone willing to implement this.

[k3d3]

Additionally, this project https://github.com/wcampbell0x2a/zerus might be worth looking at.

[JohnEmhoff]

We were able to accomplish something similar (blacklisting) by cloning the crates.io index, filtering out what we didn't want, and then pointing panamax to that filtered index when syncing. The filter itself was fairly easy to write -- maybe 100 lines of rust. I'm not sure what your precise use case is but I hope that helps.

[AlexMikhalev]

potential answer: cargo vendor only to grab project-related dependencies.