Re: [grpc-io] Updating grpc submodules

[Jan Tattermusch]

If you are using gRPC as a user (not contributing to the gRPC codebase), then using only released versions (=that have a release tag) of gRPC is the recommended approach.

Ad the "unable to remove directory": not sure what the cause is in your case, but from git perspective, tags and branches are essentially the same kind of thing internally, so using a release branch vs using a release tag likely won't change anything.

Updating submodules:

Yes, you need to update submodules yourself (that's how submodules work). Basically, run "submodule update --init" anytime you switch between commits of the grpc/grpc repository to make sure submodule are up to date. If your submodules are out of date, you likely won't be able to build.

On Tue, Oct 29, 2019 at 7:31 PM <martin...@versasec.com> wrote:

I'm using this guide to build gRPC from source. One question about the use with git. What I'm doing when a tag (v1.24.1, v1.24.2,...) is released i just checkout this tag. My first question is, is this a good approach to just working on tags. Because sometimes i'm getting errors like "unable to remove directory ....". Or is it better to be on the v1.24.x branch and pull changes from there?

Second question is how to update the submodules in the third_party folder. Do i have to update the submodules by myself? 

 

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/a602a651-8535-4e57-b5d2-ee696e92f4a3%40googlegroups.com.

--

Jan

[martin...@versasec.com]

Ok, that means I just have to make a „git submodule update —ini“ when I checkout a new release and then I have the latest sources? This error comes up when I switched from „v1.24.3“ to „v.1.25.pre“ because some submodules where deleted (libx...??)

[Jan Tattermusch]

Yes, usually you just need to run "git submodule update --init" and you're good.

The problem between 1.24.x and 1.25.x is a one time problem because we changed a submodule into a subtree. You just need to force the checkout (or delete the working copy a clone the repo again).

On Thu, Oct 31, 2019 at 3:28 PM <martin...@versasec.com> wrote:

Ok, that means I just have to make a „git submodule update —ini“ when I checkout a new release and then I have the latest sources? This error comes up when I switched from „v1.24.3“ to „v.1.25.pre“ because some submodules where deleted (libx...??)

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/bcb1d19d-0285-4d06-8864-c7a0ba6699f3%40googlegroups.com.

--

Jan