virtualgo v0.7.0 Release NotesRelease Date: 2017-09-04 // about 4 years ago
🚀 First of all if you don't know what
vgis 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 of
vgthat 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.
🚚 The main cause of issues with
vgis its usage of symbolic links. These are not supported well by go tooling (golang/go#15507, golang/go#17451). For this reason
bindfssupport has been added, which removes all of the issues caused by having symbolic links in your GOPATH. To use this you have to install
# 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
~/.virtualgodirectory. Only use
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
vgis 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-isolationflag as described there.
Other than these big changes there's also some small improvements:
vg destroynow works without arguments when inside a workspace. It will destroy the current workspace in that case.
vg destroydeactivates the current workspace if it was destroyed.
- When creating a new workspace the output contains the import mode that the new workspace uses.