commit 102d2b59e34519ae83b7a3fc8463b84fe0a7b7c3
author George Burgess IV <gbiv@chromium.org> Mon Nov 25 02:55:19 2019
committer Commit Bot <commit-bot@chromium.org> Mon Nov 25 02:55:19 2019
tree fd1b8c3157e634e6c20973b0158f1159a272c1a4
parent 8b86d754223e96acdd8ec1a38b1b570bcdf2253a

clang: package clang-tidy

In the CR for r638591, it seemed like people liked the idea of
delivering clang-tidy as a part of our regular toolchain packaging
process. Skimming the comments, my understanding is that this wasn't
done at the time in part because we weren't working with the monorepo.
Now that we're on the monorepo, it seems there aren't other blockers.

This is its own package instead of being part of the regular compiler
package, since it's assumed that:
- not all users will care about clang-tidy
- if a new bug is introduced in clang-tidy, we'd want to roll clang-tidy
  back without rolling clang back

This package is named generically, since it looks like we have a vague
want for other clang-tools-extra tools (clangd, clangd-indexer).

Going forward, the intent is to make clang_tidy_tool.py sync this
clang-tidy package by default, instead of syncing and building its own
LLVM tree to extract clang-tidy from.

Bug: 633856
Change-Id: Ied51b0d73c23a991d2545aabc06533432a3a31b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1749646
Commit-Queue: George Burgess <gbiv@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718513}