Closed tdietert closed 6 years ago
You should not ask about permission to send PR! PR for dependency loosening are welcome. And will be merged and new version and(or) revision will be released.
Great, PRs will be incoming within the next week :+1:
Hi all. @tdietert how things are going? Do you need help with this PR ? :) Similar problem exists with client-server package.
I didn't end up having the time as the abstraction I'm building on top of distributed-process-supervisor
ended up taking up all my time (and the project built just fine with allow-newer: true
in the stack.yaml file as a temporary fix.
My coworker @Acentelles may submit these PRs next week as I am out of the office for the next two weeks.
resolved with PR #11
@portnov you should be able to build both libs now with distributed-process-0.7.4
:heart:
I'm trying to build this project with the latest version of
distributed-process
(0.7.3) and currently need to increase the upper-bounds of several packages that this package depends on, and the bounds of some packages they depend on.The dependency bounds I'm interested in changing are:
The only two of these that seem to affect extra-deps (
distributed-process-X
packages) directly aretime
anddistributed-process
, which obviously also have some dependency constraints that would need reconciling.Would you be open to me submitting sweeping PRs that made these bounds changes across all the relevant
distribute-process-X
packages:as well as this one,
distributed-process-supervisor
?I'm really interested in using this package, and will for the mean time use
allow-newer: true
with stack so that I can build this library in a codebase that usesdistributed-process-0.7.3
, but would love to get these upper bounds fixed upstream and depend on these repos directly, without the use ofallow-newer
. Thanks!