On Tue, Feb 16, 2016 at 5:31 AM, Michalis Kargakis <[email protected]> wrote:
> If I have a tool in my GOPATH that uses a different version of say cobra, > wont there be a conflict? > > You still need to configure GOPATH in your tooling to prefix origin/Godeps/_workspace so that the vendored deps take precedence over directories in your GOPATH. > 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
