Profpatsch

> The first without a [+]option, the second with. Don’t you need the change information in any case in order to decide whether to apply or not? Actually my idea...

How much bloat are we talking here? A few Mbs should be totally feasible, since the rule users only fetch the tarball, not the complete git history. On Wed, Aug...

> I think we ought to work with upstream to solve the problem at that level. (See [the golden rule of software quality](http://www.haskellforall.com/2020/07/the-golden-rule-of-software-quality.html).) I love how this blogpost is already...

Though https://mail.haskell.org/pipermail/ghc-devs/2020-August/019128.html makes me suspect that until Hadrian hits we can gain a lot by shipping our own pre-extracted binary releases for now, just push to an s3 bucket from...

Especially since upstream is worrying about super-edge cases like AIX, and afaik none of the users of rules_haskell uses AIX (I didn’t even know this unix variant still existed tbh).

Did you set up your example project by using our [start script](https://haskell.build/start) as [instructed by the manual](https://rules-haskell.readthedocs.io/en/latest/)?

> Thosa are resources from the "rules_haskell" project, but I'm only using "rules_nix" in isolation. Haha, sorry, sometimes I get confused about which repository I’m looking at.

> would you accept a PR that adds building these examples to the CI via a gitlab action or similar? We are always open to PRs (especially improving examples/documentation/testsuites!). Our...

> What's provided as a build context ? I don’t understand that question :) > Is the builder blindly runs `bazel test //...` or can it be configured to call...

> Actually, just having `bazel test //...` part of bazel CI is a great improvement. We can iterate later on the removal of the test runner, if necessary. You should...