-
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
Add command to install all packages in the set #607
Comments
I think this does the job, and is a little more straightforward:
|
I was thinking about this a bit more; since Dhall is supposed to be programmable, why not just derive the I got pretty close with this:
but unfortunately this results in:
and there does not appear to be any way of filtering the |
I'd agree with the solution from @hdgarrood - the reason why that's not working with the current P.S.: well, the whole |
Now that #610 is in, I'll pivot this issue towards documenting in the README the pure-Dhall solution proposed by Harry - I'd like a new section called "Install all the packages in the set" |
I just tried using the suggested spago:
↳ ./spago.dhall
Error: Wrong type of function argument
…
{ mapValue : - { … : … }
+ < … : … >
, …
}
9│ List/map PackageAssoc Text getPackageName (toMap packages) I'm not sure if I can look into this now but I'm wondering if it's due to a Dhall or prelude version mismatch. |
It seems probable that this is the cause #594 |
I forgot to post this here previously: even after #610, I was still running into problems with the fancy Dhall approach. I don't recognise the error you are getting, so I'm not sure if it's the same one or if I just forgot what it looked like. I ended up deciding the Dhall approach was too clever and I reverted back to
which works, although you do need to rerun it each time you update your package set. |
Using |
@paulyoung you mean that the Dhall snippet in the README is incorrect in the case of a monorepo and that you have found a fix? |
@f-f yes, as I mentioned above. I've only tried it with the monorepo setup but I don't know why it would be any different. I also inlined |
Having a command that did this would make it easier to update the ecosystem when we having breaking PS releases. Another option would be to document what to execute to get the same effect.
Since I don't know Bash as well as I probably should, I found that this worked after I looked into this more:
The text was updated successfully, but these errors were encountered: