-
Notifications
You must be signed in to change notification settings - Fork 97
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
Monorepo structure and cleanup #383
Conversation
Fix link to lifted-base
Using the latest stackage lts
support GHC 8.2
Fixed link for distributed-process-async
Make the code typecheck
Add slack & use bootstrap rows over image-height formatting.
support building with GHC 8.2.1
rank1dynamic can't be built on GHC =< 7.8. This patch reflects that in dependency files.
update min GHC version
Update dependencies
Update dependencies
Update deps
…es (e.g. exceptions >= 0.10, bytestring >= 0.10)
ed788a3
to
f169b09
Compare
@davidsd This pull request is huge, so I can't expect anyone to actually review it. Would you confirm to me that your workflow still works though? Can you build e.g. I think you use Slack but I don't, so I'm not sure whether things still work. |
…ved redundant stack-ghc-9.2.4.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After adding an extra-deps
field for rematch
in the stack.yaml files, I was able to build everything. It looks good to me!
I'm not sure what's going on with the one failing test. |
Some of the tests are quite flaky. There's an option to rerun failed runs on Github actions, which I had to use a lot |
Regarding renaming this repo, I vote against. I think the name "distributed-process" makes sense, since it is the name of the "main" package here, and also the prefix of several other packages here. These are the names people will see on hackage when they search for this functionality -- they will likely not know what "cloud haskell" is unless they read some of the literature from around when cloud haskell was born. |
Makes sense, no name changes |
In the end, the website must be published from a special repo with the organization name for it to be published at |
I see you're building a bikeshed and deciding on the color! May I just comment that I've noticed some confusion around the difference between "cloud haskell" and "distributed process", and I suspect that renaming back may somehow cause additional confusion? |
@joelmccracken Do not worry, I will not rename this repository. To address potential confusion about Cloud Haskell / distributed-process, I have created an organization README: https://github.com/haskell-distributed/.github/blob/main/profile/README.md |
Beautiful, thank you! |
This is a pull request that reforms the
distributed-process
repository into a monorepo, containing most relevant packages in thehaskell-distributed organization
.See #382 for discussion
List of merged packages:
This PR also includes some cleanup, including:
CONTRIBUTING.md
file.TODO after merge: