Skip to content

Conversation

srid
Copy link
Owner

@srid srid commented Aug 21, 2025

Let's leave this as draft until I figure out a good way to use this for multi home units DX (see referenced PR below).

image

srid added a commit to juspay/vira that referenced this pull request Aug 21, 2025
This change extends multi-home units to work with tests as well. We
first make vira tests a proper spec (not executable), and then add that
to --enable-multi-repl so that the tests re-compile when the library
sources change.

This option is define in one place, ./cabal-repl. We could potentially
nixify this using srid/haskell-flake#449

Also, the tests no longer build in Nix for vira, as they require
network. Instead the Github workflow runs them through cabal.
srid added a commit to juspay/vira that referenced this pull request Aug 21, 2025
This change extends multi-home units to work with tests as well. We
first make vira tests a proper spec (not executable), and then add that
to --enable-multi-repl so that the tests re-compile when the library
sources change.

This option is define in one place, ./cabal-repl. We could potentially
nixify this using srid/haskell-flake#449

Also, the tests no longer build in Nix for vira, as they require
network. Instead the Github workflow runs them through cabal.
@srid
Copy link
Owner Author

srid commented Aug 22, 2025

Should probably rename this to cabal.components per https://discourse.haskell.org/t/cabal-terminology-sublibraries/7940/2?u=srid

I think “sublibrary” is rarely used nowadays and IMHO “component” is better. Libraries, exes, tests and benchmarks are components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant