Explain conda-forge bazel-feedstock repo structure
Takeaway: I just wanted a quick orientation to a repo I hadn't touched before, and asking 'what is this repository?' worked fine to get a fast, accurate overview.
3 sessions on bazel with a coding agent: the agent failed at least once in 2, and 1 finished without a human stepping in.
Takeaway: I just wanted a quick orientation to a repo I hadn't touched before, and asking 'what is this repository?' worked fine to get a fast, accurate overview.
Takeaway: Next time I'd start by dumping the installed packages in the build prefix earlier, since the duplicate systemlib packages were the actual root cause and cost a lot of back-and-forth with conda/python/pixi path issues.
Takeaway: Next time I'd tell the agent upfront that the target build host is linux-aarch64 (not macOS) so it skips the Docker/cross-compile detour and gets straight to patching the WORKSPACE.