-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where hpack goes so does hpack-dhall. #374
Comments
philderbeast
added a commit
to cabalism/cabal2nix
that referenced
this issue
Aug 31, 2018
philderbeast
added a commit
to cabalism/cabal2nix
that referenced
this issue
Aug 31, 2018
philderbeast
added a commit
to cabalism/cabal2nix
that referenced
this issue
Aug 31, 2018
I kept
|
|
philderbeast
added a commit
to cabalism/cabal2nix
that referenced
this issue
Aug 31, 2018
philderbeast
added a commit
to cabalism/cabal2nix
that referenced
this issue
Sep 5, 2018
When
|
philderbeast
added a commit
to cabalism/cabal2nix
that referenced
this issue
Sep 5, 2018
philderbeast
added a commit
to cabalism/cabal2nix
that referenced
this issue
Sep 6, 2018
@peti you've probably seen cabalism/hpack-dhall#3 where @sol gives some pros and cons of hpack-dhall. I liked using hpack (yaml) for filling in cabal fields for me like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the same way that we have an
--hpack
option for taking the package definition frompackage.yaml
with hpack can we also have an--hpack-dhall
option for taking the package definition frompackage.dhall
with hpack-dhall?The text was updated successfully, but these errors were encountered: