{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/vscode-go/issues/5","repository_url":"https://api.github.com/repos/Microsoft/vscode-go","labels_url":"https://api.github.com/repos/Microsoft/vscode-go/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/vscode-go/issues/5/comments","events_url":"https://api.github.com/repos/Microsoft/vscode-go/issues/5/events","html_url":"https://github.com/Microsoft/vscode-go/issues/5","id":116173790,"number":5,"title":"Should Go tools be installed to a separate GOPATH from what user has set?","user":{"login":"lukehoban","id":223467,"avatar_url":"https://avatars.githubusercontent.com/u/223467?v=3","gravatar_id":"","url":"https://api.github.com/users/lukehoban","html_url":"https://github.com/lukehoban","followers_url":"https://api.github.com/users/lukehoban/followers","following_url":"https://api.github.com/users/lukehoban/following{/other_user}","gists_url":"https://api.github.com/users/lukehoban/gists{/gist_id}","starred_url":"https://api.github.com/users/lukehoban/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lukehoban/subscriptions","organizations_url":"https://api.github.com/users/lukehoban/orgs","repos_url":"https://api.github.com/users/lukehoban/repos","events_url":"https://api.github.com/users/lukehoban/events{/privacy}","received_events_url":"https://api.github.com/users/lukehoban/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-11-10T18:41:28Z","updated_at":"2016-02-06T12:34:15Z","closed_at":null,"body":"Currently, Go tools are located and acquired based on the currently active GOPATH.  This has a few downsides:\r\n\r\n1. Go tools clutter up the users actual GOPATH even if they don't plan to use them outside of the editor\r\n2. For users with multiple workspaces, or with isolated GODEP setups per project, tools need to be downloaded into each of the workspaces\r\n\r\nInstead, the plugin could automatically install these to it's own private GOPATH and use the binaries from that location.  This could also allow the plugin to control versioning of these tools more precisely.\r\n\r\nAdditional feedback from offline discussion:\r\n\r\n> So if the plugin could grab them and everything just works out of the box with all these things installed, it actually might be pretty cool. It can also manage updates for those tools in a centralized place, rather than having them compiled at $GOPATH/bin of 10 different projects and eventually getting out of date independently.\r\n\r\nThoughts?"},"comment":{"url":"https://api.github.com/repos/Microsoft/vscode-go/issues/comments/180753010","html_url":"https://github.com/Microsoft/vscode-go/issues/5#issuecomment-180753010","issue_url":"https://api.github.com/repos/Microsoft/vscode-go/issues/5","id":180753010,"user":{"login":"ironcladlou","id":298299,"avatar_url":"https://avatars.githubusercontent.com/u/298299?v=3","gravatar_id":"","url":"https://api.github.com/users/ironcladlou","html_url":"https://github.com/ironcladlou","followers_url":"https://api.github.com/users/ironcladlou/followers","following_url":"https://api.github.com/users/ironcladlou/following{/other_user}","gists_url":"https://api.github.com/users/ironcladlou/gists{/gist_id}","starred_url":"https://api.github.com/users/ironcladlou/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ironcladlou/subscriptions","organizations_url":"https://api.github.com/users/ironcladlou/orgs","repos_url":"https://api.github.com/users/ironcladlou/repos","events_url":"https://api.github.com/users/ironcladlou/events{/privacy}","received_events_url":"https://api.github.com/users/ironcladlou/received_events","type":"User","site_admin":false},"created_at":"2016-02-06T12:34:15Z","updated_at":"2016-02-06T12:34:15Z","body":">Just a note from the peanut gallery: having multiple GOPATHs, per-project or otherwise, is nonstandard, \r\n\r\nI'm curious to understand this statement better. Multi-element GOPATH is explicitly supported as part of the handling of GOPATH since at least 1.4, and isolating project builds using project-scoped GOPATHs is a totally idiomatic in the ecosystem.\r\n\r\n>and will become increasingly rare as GO15VENDOREXPERIMENT becomes the defacto standard for dependency management.\r\n\r\nI admire your optimism... :grin: \r\n"}}