Keith Smiley

I think unfortunately this probably isn't enough to go on. If you diff the exec log or aquery output from before and after you can probably see what changed more...

I think it would still be useful to have the activation script for users who aren't using VSCode like integrations that handle this automatically. For example if you use vim...

Looks like the venv logic from uv doesn't support any of this, since it expects you to then run `uv pip` commands to actually install things. one non-ideal option would...

FWIW i think the unprocessed archive predates the quality tree artifact support in bazel in general. back in 2018 those just didn't work at all. so i imagine there is...

idk what that flag really does but should be fine to update our imports to work with and without passing it

rules_foreign_cc could definitely expose some starlark flags for this type of thing. I think using `--host_copt` does apply to some of these now, but that might be too wide for...

to workaround this you can also do a patch like this: ```bzl single_version_override( module_name = "protoc-gen-validate", patch_strip = 1, patches = [ # https://github.com/bufbuild/protoc-gen-validate/pull/1111 "//bazel/third-party:protoc-gen-validate.patch", ], ) ``` ```diff diff...

yes we could, prs welcome

This specific example would be fixed by https://github.com/bazelbuild/rules_cc/pull/245, but I suppose there might be more cases like this

Actually this example isn't fixed automatically with that change, since the _upstream_ feature also doesn't have objc-compile in that set. But with my fix I can define my custom feature...