What steps will reproduce the problem?
1. install go1.1rc1
2. setup GOPATH nicely
3. create directory of code outside GOPATH (ie, GOPATH=/home/user/go and directory is
/home/user/some-project) -- make sure it contains some remote dependencies
4. enter directory and type "go get" to download dependencies prior to
"go build"


What is the expected output?
With go1.0.3, the behavior was as described by "go help gopath", in that
"go get" downloaded all dependencies of the project in the current directory
to the first directory in $GOPATH.


What do you see instead?
With go1.1rc1, "go get" now errors out with "go install: no install
location for directory /home/user/some-project outside GOPATH".


To be clear, I am not necessarily taking issue with the new behavior, but do believe it
should be noted in the go1.1 migration document and with more clear language in one of
"go help gopath" and/or "go help get".

Also, the previous behavior was very convenient, so if there is an easy workaround for
go1.1 (assuming this new behavior is intended) short of moving the code into some part
of GOPATH (which would require more strict structure), I'd love to hear about it.

Of course, as always and should be expected, I am happy to provide any further
clarification or information necessary or possible.