Andreas Herrmann

@coeuvre I see this is labeled as `awaiting-PR-merge` but not yet merged. Is it stuck on anything internally? Anything I can help with to get this merged?

Thank you for reporting this @kozak! > I think that `bazel` shouldn't be processing `BUILD.bazel` files of dependencies ? That's a tricky issue, unfortunately there's no way to make Bazel...

@jonathanlking Thank you for testing `--deleted_packages` and reporting back! As mentioned before I fear there is not much else we can do about this issue in rules_haskell, so, I'm closing...

@layus What's the status on this one? What do you need to push it over the finish line?

I've added a comment to the clodl PR https://github.com/tweag/clodl/pull/48#issuecomment-2059088567

@Jonpez2 Perhaps yes, though this may still require additional metadata: To achieve fine granularity the set `[the-nix-packages-you-told-me-you-depend-on]` would need to be minimal for each action. So, it's not one global...

> I have not fully thought this through, but it seems to be that unless the change would be placed in Bazel code itself (sic!), all of existing rules would...

> There is another way to move forward, which I feel is a bit more lean and less disruptive towards overall Bazel build model. > > Bazel has [Remote Assets...

I'm currently a bit overloaded on other work and OOO due to an accident. I haven't managed to catch-up on the discussion above, yet. I haven't forgotten it and I...

Sorry for the long silence on this one. I've been quite busy lately. > Do all actions happen within the context of some particular posix toolchain by any chance? @Jonpez2...