https://bugzilla.redhat.com/show_bug.cgi?id=1301143
Antonio Murdaca <amurdaca(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(amurdaca(a)redhat.c |
|om) |
--- Comment #20 from Antonio Murdaca <amurdaca(a)redhat.com> ---
(In reply to Jan Chaloupka from comment #19)
After reading [1] I can not figure out why is GO15VENDOREXPERIMENT
env
needed. Can you help me to understand?
[1]
https://docs.google.com/document/d/1Bz5-UB7g2uPBdOx-
rw5t9MxJwkfpx90cqG9AFL0JAYo/edit
Quoting from the doc:
This change will only be enabled if the go command is run with
GO15VENDOREXPERIMENT=1 in its environment.
So, the behavior of looking into $pwd/vendor/... instead of resolving deps from
$GOPATH is only enabled if you pass that env variable - otherwise it uses
$GOPATH (and maybe $GOROOT). This is in go1.5, eventually we will have this as
the default behavior in go1.6, from the doc:
If we decide that the vendor behavior is correct, then in a later release
(possibly Go 1.6) we would make the vendor behavior default on. Projects
containing “vendor” directories could still use “GO15VENDOREXPERIMENT=0” to get
the old behavior while they convert their code. In a still later release
(possibly Go 1.7) we would remove the use of the environment variable, locking
in the vendoring semantics.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component