On 02/16/2016 11:31 AM, Michalis Kargakis wrote:
If I have a tool in my GOPATH that uses a different version of say cobra,
wont there be a conflict?
From my experience you will, I was just hit by this. I had different
version of k8s build locally and then when trying to build origin
I was getting an error about k8s deps which has changed upstream :/
Cleaning GOPATH/pkg helped, but that's way too problematic imho to
remember doing this with every make.
Maciej
On Mon, Feb 15, 2016 at 6:22 PM, Clayton Coleman <[email protected]>
wrote:
It shouldn't.... what do you mean?
On Mon, Feb 15, 2016 at 11:55 AM, Michalis Kargakis <[email protected]>
wrote:
This means that we need to work on a separate GOPATH just for Origin :)
On Mon, Feb 15, 2016 at 4:06 PM, Clayton Coleman <[email protected]>
wrote:
While simplifying the build steps (to no longer create a fake GOPATH
under _output and thus work more effectively with other tools) in
https://github.com/openshift/origin/pull/7281, it may cause you to
have trouble running `make clean build` if you have a custom GOPATH
with older files in GOPATH/pkg (at the root of your normal directory).
If you experience any weirdness where a clean build doesn't appear to
be clean, try removing the `pkg/` directory under the root of your
GOPATH.
_______________________________________________
dev mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
_______________________________________________
dev mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
_______________________________________________
dev mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
