You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
haskellProjects.foo={devShell.enable=false;packageSet={# The overlays are composed in the order they are shown here.base=pkgs.haskell.packages.ghc944;local={mypkg.root=./.;# Assumes mypkg.cabal};source-overrides={..};# Overrides by direct path to sourceoverrides=self: super: {..};# Raw Haskell overlay};};
Users can then use config.haskellPackages.foo.packageSet.final to access all the packages. The idea is that we can say "start from base", then we apply local, then source-overrides and finally overrides, before creating the project specific haskell package set.
finalPackages of #68 would become packageSet.final.
The text was updated successfully, but these errors were encountered:
I'm not convinced yet, because it makes the syntax a little bit more complicated. I think of a haskellProject as a package set, and if I need more than one package set, I need to use multiple projects anyway.
We don't have a module for warnings / assertions support yet, but that could be added in flake-parts.
because it makes the syntax a little bit more complicated. I think of a haskellProject as a package set, and if I need more than one package set, I need to use multiple projects anyway.
Detached from #52 (comment)
Users can then use
config.haskellPackages.foo.packageSet.final
to access all the packages. The idea is that we can say "start frombase
", then we applylocal
, thensource-overrides
and finallyoverrides
, before creating the project specific haskell package set.finalPackages
of #68 would becomepackageSet.final
.The text was updated successfully, but these errors were encountered: