Open altendky opened 4 years ago
Cool -- that workflow definitely sounds like one I want to work for people (FWIW I do this "manually", which is why I didn't notice it didn't work -- by which I mean I have a bootstrap script for new machines that just runs the single untracked venv of mine -- i.e. virtualenv ~/.local/share/virtualenvs/venvs && ~/.local/share/virtualenvs/venvs/bin/pip install venvs
but that's because I was lazy and didn't set this up yet, so yeah +1 for filing, we should fix this.
Possibly though we should make venvs
's virtualenv "special" though -- like give it its own config syntax or something, because otherwise yeah the reason this blows up is that it wants to now recreate the venv but then blows itself up when it went and deleted all its own files, so we need some other atomic upgrade to happen there.
My intended workflow is to have my
virtualenvs.toml
in my home directory git repo. When I get a new computer I should be able to setup that repo then grab the shiv artifact and run converge. From there on I should be able to run the~/.local/share/virtualenvs/venvs/bin/venvs
executable to converge etc.For now I'll just comment out the venvs env once it gets installed the first time.