Ulf Adams

Well, that might be easy to answer. The reason I added `BAZEL_TRACK_SOURCE_DIRECTORIES` back then was because `glob` converts filenames into labels, and there are file names that aren't valid labels,...

cc_binary with .so is currently special, but cc_binary doesn't handle .a. One of the downsides of special-casing the specific filename is that it's not cross-platform compatible. One option would be...

I think it's very easy to mess up the dependencies. Consider for example a workspace that has two cc_library and two cc_export rules, with each of the cc_export rules depending...

I'm not saying that they aren't. But I think it's a problem that it's a runtime error rather than a compile-time error. If we can make it a compile-time error,...

Consider that many debian packages come with both .so and .a which allows developers to decide after the fact whether to link a specific library statically or dynamically.

How about publishing the doc now, and having the discussion on bazel-discuss?

Our CI is failing regularly with a similar error message even *with* internet access. It seems like api.github.com is unreliable? This is a concern because GitHub installs bazelisk at least...

@fenollp Is that documented anywhere?

Agreed. It looks like that was done (#599) to remove the requirement to have wget installed, so it may not have worked before that either since wget presumably also requires...

Given that plain debian buster doesn't work anyway (no C++ compiler, no Java toolchain, no Go, no ...), maybe the right thing to do is to improve error handling and...