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

Update templates to use a newer LTS. #205

Open
lowderdev opened this issue Sep 15, 2021 · 6 comments
Open

Update templates to use a newer LTS. #205

lowderdev opened this issue Sep 15, 2021 · 6 comments

Comments

@lowderdev
Copy link

I was recently trying to setup a yesod project and ran into this issue with ghc and macOS Big Sur.

The current yesod templates resolve at lts-16.31, which uses ghc 8.8.4, which doesn't include the Big Sur fix.
We were able to update to lts-18.10 with these changes.

Are these updates we could make to this repo so that newer yesod projects can benefit from newer versions of ghc and various packages?

I'd be happy to contribute to this, although I'm very much a beginner Haskeller and would likely require a lot of guidance. 😅

@snoyberg
Copy link
Member

Definitely updates we could make! Most likely it's just a matter of updating the upper bounds on package requirements. If you'd like to take a crack at it, that would be awesome. Happy to provide guidance, though for personal reasons it may be more sporadic than usual.

@lowderdev
Copy link
Author

Awesome! I'll take a stab. :)

@StevenXL
Copy link
Member

StevenXL commented Aug 7, 2022

I too was wondering about updating the LTS to the latest. After using the current template for yesodweb/postgres, I ended up deleting all the bounds in package.yaml and updated stack.yaml to use LTS 19.17. Then I ran stack build and stack exec -- yesod devel and things seem to be working.

Is this not a thing we can do? I thought that the point of a snapshot is that it locks down the packages to specific versions; why (re)state the versions in the package.yaml?

Oh yea - I also had to add some language pragmas to _Models.hs.

@snoyberg
Copy link
Member

snoyberg commented Aug 8, 2022

The scaffold doesn't include the stack.yaml in it, we use package.yaml to guide Stack to choose a compatible resolver.

@StevenXL
Copy link
Member

StevenXL commented Aug 8, 2022

The scaffold doesn't include the stack.yaml in it, we use package.yaml to guide Stack to choose a compatible resolver.

Thanks Michael. I guess I could take a look at my project's 'stack la dependencies', update 'package.yaml', and let Stack do the rest.

I'll give it a shot whenever I can. Right now I have a 5-month old that refuses to nap! 😅

@snoyberg
Copy link
Member

snoyberg commented Aug 9, 2022

Right now I have a 5-month old that refuses to nap!

I can fully relate to this statement :)

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

No branches or pull requests

3 participants