Re: [go-nuts] git submodule vs normal go vendoring

2017-10-03 Thread paul . totterman
> > If the upstream goes away, you can just re-publish the repo (which you'll > have cloned locally) and adjust the remote URL in .gitmodules. New people > cloning will get the clone from the new source. > Not to counter anything you've said, but dep also allows adjusting the URL. Gopkg.toml:

Re: [go-nuts] git submodule vs normal go vendoring

2017-10-03 Thread Sam Vilain
In theory, the git submodule builds are *more* reproducible, because all your build servers etc have clones of those sub-repos cached under their .git, even though they are not under your control. If the upstream goes away, you can just re-publish the repo (which you'll have cloned locally) and ad

Re: [go-nuts] git submodule vs normal go vendoring

2017-10-01 Thread Peter Mogensen
On 2017-10-01 06:38, JM wrote: > can anyone tell me the pros/cons of using git submodule update instead > of godep govendor etc... ? > > git submodule update --init --recursive Your build depend on that command succeeding. If sub-repos are not under your control that can be a serious problem fo

[go-nuts] git submodule vs normal go vendoring

2017-09-30 Thread JM
can anyone tell me the pros/cons of using git submodule update instead of godep govendor etc... ? git submodule update --init --recursive -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails f