`glide update` or a install should do the job, yes.
If that does not `mv vendor _vendor && glide install` to figure out if
things works or are stinky.
Do you mean you re in situation where you have one to many repo to update
by doing a fork / PR / merge
to actually make a significant change
Can it work when the forked gh repo contains many packages that sometimes
use each other?
It feels weird to be masking the very repo I cloned to work in...
Now I am using the approach outlined by Francesc Campoy in
http://blog.campoy.cat/2014/03/github-and-go-forking-pull-requests-and.html
Neat bu
I did try it but perhaps I did something wrong.
Is 'glide update' enough after such an addition?
The cloned repo has a glide.yaml and lock file checked in so these would
have to be kept local or otherwise skipped in pull requests I guess.
On Thu, Sep 1, 2016, 23:43 mhhcbon wrote:
> this helps ?
this helps ?
https://github.com/Masterminds/glide/blob/a20b232c135529d4d73b5cf95f66954d34750ced/docs/example-glide.yaml#L30
Le jeudi 1 septembre 2016 22:15:27 UTC+2, Henrik Johansson a écrit :
>
> Hi,
>
> How does the aliasing support in Glide work.
> There is a couple of hints in the Github read
