Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add options for project which wish to make modifications to deps and use the mods when building. #6

Open
DiamondLovesYou opened this issue Apr 7, 2016 · 2 comments

Comments

@DiamondLovesYou
Copy link

Useful in case one needs to make a modification to a dependencies source, and would like to subsequently use the edited checkout instead of a cargo managed checkout.

Ie:

# --umbrella puts the repo in one level higher than highest level cargo project
# ie if your project was at /foo/bar/far, where 'far' is a nested crate inside bar, 
# cargo clean should checkout the project to /foo/project-name.
#
# --override-dep adds a cargo config path entry for the project;
# using the previous example, the config file is placed so it overrides 'bar' 's deps when 
# --umbrella is given, else the project present in the current dir.
cargo clone --umbrella --override-dep
@JanLikar
Copy link
Owner

JanLikar commented Apr 8, 2016

Thank you for reporting the issue. I'm currently not doing a lot of open source development, so this might take a while.

@JanLikar
Copy link
Owner

JanLikar commented Jan 3, 2022

Implementing "editable checkouts" does require cloning, but I think its purpose is orthogonal to the purpose of cargo-clone. I think this should be a separate subcommand, possibly having cargo-clone as its dependency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants