On Thu, 20 Jul 2017 03:08:58 -0700 (PDT)
"'Florian Uekermann' via golang-nuts" wrote:
> The go tool does not provide a way to update
> dependencies of packages that are not go get-able.
Yes it is. Go tooling is based on and has a convention to follow. Hence there
is no support for "place pieces
See my previous answer to ohir for a less convoluted and less specific
problem statement. My problem does not seem to be related to being inside
or outside a GOPATH.
> Dependencies are derived from import paths. Import paths are not complete
> paths. They are transformed to complete paths by
Thanks for the suggestions. I may not have explained the setup well enough.
I don't think your suggestions work if you just have your code in a folder
without any additional structure (no src directory).
But your first suggestion prompted my to play around with having the
package in a GOPATH and
On Wed, Jul 19, 2017 at 8:45 PM 'Florian Uekermann' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> tldr: Please let me update dependencies of packages that are in arbitrary
directories.
Dependencies are derived from import paths. Import paths are not complete
paths. They are transformed
On Wed, 19 Jul 2017 11:45:00 -0700 (PDT)
"'Florian Uekermann' via golang-nuts" wrote:
> tldr: Please let me update dependencies of packages that are in arbitrary
> directories.
1. You may add your current "arbitrary" to the local environment GOPATH
as in
export GOPATH="$GOPATH:/arbitrary/src"
Hi everyone,
I never bothered too much with the details of "go get" until the issue
recently came up in a conversation with another developer who was also
annoyed by the clumsiness of the go tool in practice. I often work with
programs that are not in a GOPATH, but import some non-local package
