moving .git directory/file breaks things about gvm HOT 2 CLOSED

I swear there was a good reason for doing that...

Sent from my iPhone

On Feb 21, 2014, at 4:38 PM, Bill Wanjohi [email protected] wrote:

Hi guys, love the project. I use gvm a lot, but I like to install it with git-only. This is very actually very simple; I just need to clone the repository to ~/.gvm and add the following to my rc script:

export GVM_ROOT=$HOME/.gvm
source $GVM_ROOT/scripts/gvm-default
My problem is that the gvm script intentionally hides the .git directory, making git pulls cumbersome, and making the directory unrecognizable as a git repository to configuration management tools. This is described as a safety feature in this commit: 85db830, but without any explanation of the risks averted.

Issue #7 alludes to this as a nuisance that is worked around, but would it be possible to just remove this behavior, and allow for the dynamic management of the gvm installation?

—
Reply to this email directly or view it on GitHub.

from gvm.

Ok I remembered now. There were issues with imports that use git paths. Something about having a git repo nested inside another git repo was causing problems so I move gvm's .git folder out of the way unless it's being updated.

from gvm.