-
Notifications
You must be signed in to change notification settings - Fork 132
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
Autoinstall missing packages #1211
Comments
I considered this before (I would have called the flag So in the end I am not sure it would be actually more convenient than having the commands printed there? |
BTW, could you explain a bit more: it seems that E.g. https://github.com/garganscript/purescript-sequences/blob/spago-next/spago.yaml I added only So I'm a bit confused what to put in |
@CGenie the publishing checks include verifying that the dependencies of your package are accurate, so that:
These are both situations that you would not easily detect when just writing code. They are also not critical, in the sense that during normal development you might only care about your package compiling, rather than the project manifest being 100% accurate. It's possible to have Spago check this for you on a one-off basis, by enabling the The default situation is that Spago does not check until it's required, which is at the time of publishing your package - this is what just happened to you |
Btw, the reason why you can have only Running |
Thank you! |
I will close this for now since I am still holding the opinion that I detailed above, but let's reopen it if the inconvenience gets too big 🙂 |
Instead of suggesting the user to copy-paste the command from the terminal, like here:
a flag could be added, e.g.
spago install --missing
to install these automaticallyThe text was updated successfully, but these errors were encountered: