aiuto
commented
3 years ago Off the top of my head, I see a few user journeys
- I have a Linux only repo and I create RPMs: -> fail hard at workspace resolution if we can not find rpmbuild
- I have a mixed OS repo and I expect
bazel build|test ...to work.- we obviously can't fail hard, we have to do incompatible target skipping
- I have a mixed OS monorepo but my developers have slices for each OquS.
- should blaze build //foo/bar:bar.rpm work for a Windows user?
- what if you are using remote build? Even though the toolchain can not resolve in your workspace, it might on the build machine.
The first question is what important patterns is this missing.
In https://github.com/bazelbuild/rules_pkg/pull/254#discussion_r553615765, I brought up the point that we don't really have a great way to pass warnings WRT toolchain resolution from the repository rule up to the rule(s) that utilize the toolchain: the warnings can be displayed far away from the actual error that occurs
Consider investigating ways to improve the UX here.