Not sure what you mean. go get -u fetches and updates all dependencies it
finds.
On Mar 18, 2014 2:55 AM, "Glyn Normington" <notifications@github.com> wrote:

> In README.md:
>
> > +Extend `$GOPATH` and `$PATH`:
> > +```
> > +# export GOPATH=/root/go:$GOPATH
> > +# export PATH=$PATH:/root/go/bin
> > +```
> > +
> > +Install [godep](https://github.com/kr/godep) (used to manage garden's dependencies):
> > +```
> > +# go get github.com/kr/godep
> > +```
> > +
> > +Get garden and its dependencies:
> > +```
> > +# go get github.com/pivotal-cf-experimental/garden
> > +# cd /root/go/src/github.com/pivotal-cf-experimental/garden
> > +# godep restore
>
> Isn't there still a missing step in development? Suppose someone adds a
> new dependency (on another machine). go get -u ../... will fetch and
> fast-forward all the *known* dependencies, but won't pick up the new
> dependency. Wouldn't it be better to control and communicate upgrades using
> godep in development? Otherwise we'll need a "word of mouth" approach which
> won't scale to distributed development or where there are unknown third
> parties doing development on forks.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/pivotal-cf-experimental/garden/pull/5/files#r10696044>
> .
>