This is a big change in the design of virtualgo. Before you could import from
your global gopath by default. This has now been changed for newly created
workspaces. Old ones keep working the same and you can still force the old
behaviour when creating a workspace by running vg init --global-fallback.
The only packages that you can use are the ones inside the workspace. However,
a command is also added to install a local packge inside the workspace, this
solves #5.
The name of this command is localInstall, see the updated README for usage.
I'm content with the name, but not super happy it. Any suggestions for better
names are appreciated.
The README has been updated as well to reflect the new changes, but also to
explain right at the start why vg is so great. Any changes/typos are also
appreciated.
After this is finalized and merged a new release should be done as this marks a
big change in vg usage.
One more thing I'm not certain about is if localInstall should be persistent over vg ensure by default. I think it's a nice feature to have with a --persistent flag, but maybe by default vg ensure should overwrite it.
This is a big change in the design of virtualgo. Before you could import from your global gopath by default. This has now been changed for newly created workspaces. Old ones keep working the same and you can still force the old behaviour when creating a workspace by running
vg init --global-fallback
.The only packages that you can use are the ones inside the workspace. However, a command is also added to install a local packge inside the workspace, this solves #5.
The name of this command is
localInstall
, see the updated README for usage. I'm content with the name, but not super happy it. Any suggestions for better names are appreciated.The README has been updated as well to reflect the new changes, but also to explain right at the start why
vg
is so great. Any changes/typos are also appreciated.After this is finalized and merged a new release should be done as this marks a big change in
vg
usage.One more thing I'm not certain about is if
localInstall
should be persistent overvg ensure
by default. I think it's a nice feature to have with a--persistent
flag, but maybe by defaultvg ensure
should overwrite it.