Changelog History
-
v0.9.0 Changes
January 02, 2019๐ Improvements
- ๐ Allow using $VIRTUALGO_ROOT to set the directory where environments are stored. By default this is still
~/.virtualgo
๐ Fixes
- Return status code in the PROMPT_COMMAND
- Don't set the same prompt_command if it's already there.
- ๐ Allow using $VIRTUALGO_ROOT to set the directory where environments are stored. By default this is still
-
v0.8.0 Changes
December 20, 2017๐ Improvements
- ๐ Scripting with
vg
is now much better supported.vg
should now keep working even when you have runset -eux
before. - ๐ Starting with this release binaries for some architectures are precompiled, in case you want to pin a specific version of
vg
for your CI. - โ
A test suite with coverage is now run on Travis. This should give more confidence that changes don't break
vg
. - Some error messages have been improved with much more detailed steps that should be tried to fix the issue.
๐ Fixes
- ๐ Scripting with
-
v0.7.2 Changes
October 02, 2017- ๐ Fix issues caught by shellcheck
-
v0.7.2-test Changes
December 20, 20172017-12-20
-
v0.7.1 Changes
October 02, 2017- ๐ Fixed an issue in using
bindfs
on OSX
- ๐ Fixed an issue in using
-
v0.7.0 Changes
September 04, 2017๐ First of all if you don't know what
vg
is yet, just check the README, which is much more informative in that case. Otherwise these release notes contain the changes to the previous major release ofvg
that you should know about.โฌ๏ธ How to upgrade
go get -u github.com/GetStream/vg
โก๏ธ Afterwards, restart all your shells to make sure it's using the updated version.
๐ Changes
๐
bindfs
support๐ The main cause of issues with
vg
is its usage of symbolic links. These are not supported well by go tooling (golang/go#15507, golang/go#17451). For this reasonbindfs
support has been added, which removes all of the issues caused by having symbolic links in your GOPATH. To use this you have to installbindfs
though:# OSXbrew install bindfs# Ubuntuapt install bindfs# Arch Linuxpacaur -S bindfs # or yaourt or whatever tool you use for AUR
๐ There's one important thing if you do this though. DON'T remove things manually from the
~/.virtualgo
directory. Only usevg destroy
/vg uninstall
, otherwise you can very well lose data.0๏ธโฃ Global fallback import mode is the default again
๐ Support for full isolation was added in the previous version (v0.6.0). This was made the default, because it seemed like a really useful feature. However, after more usage by more people it turned out that some things stopped working as expected. Since one of the main goals of
vg
is that you should be able to use your tools as before this was considered a big issue.โช The worst of these issues were caused by the usage of symbolic links, which are thus fixed now. Sadly, some others remained present. Luckily, the remaining issues have simple workarounds. However, without knowing about the issues confusion will likely occur as some common commands don't work as expected. This was still considered a big enough issue that the default for new workspaces has been reverted to "global fallback" import mode. A more thorough explanation of the issues and workarounds can be found in this section of the README.
0๏ธโฃ One important thing to keep in mind is that existing workspaces won't be changed automatically. If you want to use the new default for existing workspaces you should recreate them:
vg destroy example vg activate example
If after reading the section from the README you still want to use full isolation, you should create new workspaces with the
--full-isolation
flag as described there.Small changes
Other than these big changes there's also some small improvements:
vg destroy
now works without arguments when inside a workspace. It will destroy the current workspace in that case.vg destroy
deactivates the current workspace if it was destroyed.- When creating a new workspace the output contains the import mode that the new workspace uses.