cargo new: add config option to force-create vcs when inside an existing vcs

[diogobaeder]

Hey guys,

I've created a ~/.cargo/config file in which I've set the configs I needed; however, even if I put vcs = "git" there, when I create a library with cargo new mylibrary it doesn't create the repo as well - unless I explicitly pass the argument --vcs git.

From what I saw in other issues open here, and from conversation elsewhere, it might be related to the fact that my home directory is also a repository (which I use to selectively version some files).

Any clues?

Thanks!

P.S.: I'm just starting to learn Rust, and so far I'm loving it! Great job everyone! :-)

[lukaslueg]

This is expected behavior. When you call "cargo new" with no explicit vcs-option, it walks up the current path and figures out that the project is being created within an already existing repository (your ~). In that situation, cargo will not create a new repository (the default use case being that you create a sub-package in an already existing repo). The explicit --vcs git overrides this, vcs = "git" does not.

[alexcrichton]

Ah yeah I think @lukaslueg hit the nail on the head, so I'm going to close. Thanks for the report regardless!

[diogobaeder]

FWIW, it would be useful if there was a config to make it force the creation of a repo. I'm pretty sure I'm not the only one to version their home dir. But anyway, this would be a feature request, not a bug.

[alexcrichton]

Ok!

[diogobaeder]

Thanks for the consideration, Alex! :-)