android_mt6572_jiabo/prebuilts/tools/linux-x86_64/kythe/third_party
2025-09-05 16:56:03 +08:00
..
bazel first commit 2025-09-05 16:56:03 +08:00
external first commit 2025-09-05 16:56:03 +08:00
grpc first commit 2025-09-05 16:56:03 +08:00
grpc-java first commit 2025-09-05 16:56:03 +08:00
gson first commit 2025-09-05 16:56:03 +08:00
hpack first commit 2025-09-05 16:56:03 +08:00
jcommander first commit 2025-09-05 16:56:03 +08:00
jsr305_annotations first commit 2025-09-05 16:56:03 +08:00
leiningen first commit 2025-09-05 16:56:03 +08:00
leveldb first commit 2025-09-05 16:56:03 +08:00
llvm first commit 2025-09-05 16:56:03 +08:00
netty first commit 2025-09-05 16:56:03 +08:00
proto first commit 2025-09-05 16:56:03 +08:00
rapidjson first commit 2025-09-05 16:56:03 +08:00
re2j first commit 2025-09-05 16:56:03 +08:00
snappy first commit 2025-09-05 16:56:03 +08:00
zlib first commit 2025-09-05 16:56:03 +08:00
README first commit 2025-09-05 16:56:03 +08:00

All third_party libraries are available at http://kythe.io/repo/third_party/

To add a new component to this third_party directory, follow these steps:

1) Have a discussion on kythe-dev mailing list;
2) Provide a clear rational in the change adding the third_party code;
3) Add the third_party code in a patch containing no other changes;
4) Add a third_party/<projectxyz>/README.google file listing:
     * The URL to the package version
     * The Version
     * The License
     * The path to a LICENSE file (create one if it does not exist)
     * A brief Description
     * A list of Local Modifications
5) Ensure //third_party:licenses includes the component's license.
6) Have the change reviewed by multiple people in the team.

Thank you.