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

Pull the latest package set version when doing `init` #254

f-f opened this issue Jun 6, 2019 · 0 comments


None yet
1 participant
Copy link

commented Jun 6, 2019

Right now when you do spago init, the package set you get is the one in the template bundled with the binary. We have @spacchettibotti keeping it up to date, but this means that if you have an old version of spago but a new version of purescript you're going to run into version-mismatch-errors (basically #225 and friends)

I propose that we pull the latest package set instead, and use the bundled one as a fallback.
To do this we could just run spago package-set-upgrade under the hood. This is currently quite slow and does not check if we are already on the latest version (i.e. it's slow every time), so it would be nice to do it too so it becomes a no-op if the package set version is the latest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.