Skip to content
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

[etlas] Migrate to hpack #642

Closed
rahulmutt opened this issue Feb 6, 2018 · 5 comments
Closed

[etlas] Migrate to hpack #642

rahulmutt opened this issue Feb 6, 2018 · 5 comments

Comments

@rahulmutt
Copy link
Member

https://github.com/sol/hpack is a wonderful tool to convert yaml files into Cabal files. The syntax for Cabal files can be adhoc at times so having something structured and standardized like yaml seems like a great fit. It seems like a great idea for Etlas to make a yaml-like format the default.

@NickSeagull
Copy link
Collaborator

Another interesting idea would be if etlas handled the conversion to the cabal file internally.

I mean, no cabal file would be generated in the root of the project, or at least unless specified. This would lead to less confusions in my opinion. "Why do you have two project config files?"

@rahulmutt
Copy link
Member Author

That was intended above - I was probably not clear. The idea is to eventually move to a package.yaml file as the default at the root of the directory. No need to even use a Cabal file internally - all you need is a user-facing representation of the build model and parsing a package.yaml is enough for that.

@jneira
Copy link
Collaborator

jneira commented Mar 20, 2018

Maybe we can consider the use of dhall instead (directly or using dhall-to-cabal), as commented in #704.

@NickSeagull
Copy link
Collaborator

I like dhall, but sometimes it looks really verbose. We should abstract stuff from it.

@jneira
Copy link
Collaborator

jneira commented Aug 10, 2018

Well i think that finally dhall would be the chosen format (see typelead/etlas#66) so it seems we can close this one.

@jneira jneira closed this as completed Aug 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants