[llvm-dev] RFC: Contributing Bazel BUILD files in the "peripheral" support tier

[Stefan Teleman via llvm-dev]

On Fri, Dec 4, 2020 at 11:32 PM Mehdi AMINI via llvm-dev
<llvm-dev at lists.llvm.org> wrote:

> Another spin to it: the point of working on the policy and putting it in place was also to help make sure that such proposals aren't automatically controversial to the point where we can't resolve them. If the policy does not help us here, that's quite a failure IMO.

This proposal isn't controversial because of the policy.

As a matter of historical record, this new policy was shoehorned into
existence ex post facto, after the Bazel build system decision had
already been made, and because some people - myself included -
objected to the proposal. The policy doesn't address the potentially
infinite proliferation of build systems and build system files in
LLVM. Quite the opposite.

And since you asked: my objections remain the same.  In my opinion,
Bazel build system infrastructure files do not belong in the LLVM tree
anymore than GN, or autoconf, or rpm specs, or Solaris pkg specs do.

Folks who want to use Bazel to build LLVM can accomplish their goal by
creating an overlay Git repo containing and providing the Bazel build
files from there. That approach would simplify life for everyone.
There would be no need for this tiered support policy, and there's
nothing controversial about having an overlay Git repo independent of
LLVM. Anyone can create their own overlay build system repo containing
build files for their favorite build system. It doesn't require LLVM
consent.

-- 
Stefan Teleman
stefan.teleman at gmail.com