-
Notifications
You must be signed in to change notification settings - Fork 89
Move to get Haskell packages from CHaP #4078
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
Conversation
It doesn't have to be blocked: use a |
Note that |
ok, I will chase this up on Monday. |
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.
it went green!
Now at least it builds. Left to do is to remove one srp at the time so see if we can improve on the situation. |
I think we could merge this as is and then work from this point? any objections? |
I am just trying to see if the new io-sim packages help. |
But perhaps you made a good point that it can be done in a separate PR |
I just tried that and they don't work with the version of |
Ok, let's call this done. We will improve on it later. |
We just got compatible typed-protocols published, I'm just trying to see if I can roll that into this also. |
Worked locally, pushing it. |
By reading the new text in |
@nfrisby if you read it and you don't understand, then I regard that as a deficiency in the text and please say so :) you might also need to read the CHaP readme, which is linked. |
@coot is this good to go? |
@michaelpj this is only about using CHaP, not releasing anything to it, right? The next version of packages from this repo needs to be released from the |
@coot correct, we are only replacing |
Yes, this doesn't say anything about how you release your packages. It should help with releasing packages, in that if you have a "clean" cabal.project with CHaP, then you know that your released package will build downstream without any additional config. However, I'm not sure it's worth backporting these changes to the release branch just for that! We can do what we need to do for the 1.35 release and just take this forward on master. |
|
bors try |
This moves the repository to use cardano-haskell-packages (CHaP) repository.
So close. It went green but conflicts with #4103. Rebased to fix conflicts. |
tryTimed out. |
1 similar comment
tryTimed out. |
bors try |
tryBuild failed: |
|
bors retry |
bors merge |
no idea if that will work |
hallelujah |
4148: Add simple `hie.yaml` r=amesgen a=amesgen # Description This is necessary due to a bug somewhere in HLS 1.7 vs 1.8, which was upgraded in #4078. Co-authored-by: Alexander Esgen <[email protected]>
4148: Add simple `hie.yaml` r=amesgen a=amesgen # Description This is necessary due to a bug somewhere in HLS 1.7 vs 1.8, which was upgraded in #4078. Co-authored-by: Alexander Esgen <[email protected]>
This moves the repository to use cardano-haskell-packages (CHaP) repository.
This is currently blocked by input-output-hk/io-sim#37. CHaP had been pre-populated with the dependencies of the lastest release of cardano-node, but ouroboros-network has progressed in the meantime requiring a newer version of io-sim which is not in CHaP yet.