GitHub user chhsia0 opened a pull request:
https://github.com/apache/mesos/pull/224
Bundled gRPC v1.4.2 into 3rdparty libraries.
The bundled package is generated with the following command:
git clone -b v1.4.2 https://github.com/grpc/grpc.git grpc-1.4.2
(cd grpc-1.4.2 && git submodule update --init third_party/benchmark \
third_party/cares third_party/gflags)
tar zcvf grpc-1.4.2.tar.gz --exclude .git grpc-1.4.2
We download gRPC from GitHub instead of using the official tarball
because we need to use `git submodule` to download dependent 3rd party
packages for gRPC, and the necessary git metadata does not exist in the
official tarball.
gRPC also depends on openssl, protobuf 3.x and gperftools (unless using
CMake). Since we have already bundled the latter two, the only system
dependency is openssl.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chhsia0/mesos grpc-bundle
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/mesos/pull/224.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #224
----
commit 16e85ccd02d32a23e4a22a67625ba6000da499b5
Author: Chun-Hung Hsiao <[email protected]>
Date: 2017-05-22T23:30:59Z
Bundled gRPC v1.4.2 into 3rdparty libraries.
The bundled package is generated with the following command:
git clone -b v1.4.2 https://github.com/grpc/grpc.git grpc-1.4.2
(cd grpc-1.4.2 && git submodule update --init third_party/benchmark \
third_party/cares third_party/gflags)
tar zcvf grpc-1.4.2.tar.gz --exclude .git grpc-1.4.2
We download gRPC from GitHub instead of using the official tarball
because we need to use `git submodule` to download dependent 3rd party
packages for gRPC, and the necessary git metadata does not exist in the
official tarball.
gRPC also depends on openssl, protobuf 3.x and gperftools (unless using
CMake). Since we have already bundled the latter two, the only system
dependency is openssl.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
