darcs

Patch 1929 document why we can't bump the shelly de... (and 3 more)

Title document why we can't bump the shelly de... (and 3 more)
Superseder Nosy List ganesh
Related Issues
Status accepted Assigned To
Milestone

Created on 2019-09-20.18:58:50 by ganesh, last changed 2019-09-25.21:05:00 by ganesh.

Files
File name Status Uploaded Type Edit Remove
document-why-we-can_t-bump-the-shelly-dependency.dpatch ganesh, 2019-09-20.18:58:49 application/x-darcs-patch
patch-preview.txt ganesh, 2019-09-20.18:58:49 text/x-darcs-patch
patch-preview.txt ganesh, 2019-09-22.11:56:43 text/x-darcs-patch
support-hashable-1_3.dpatch ganesh, 2019-09-22.11:56:43 application/x-darcs-patch
unnamed ganesh, 2019-09-20.18:58:49 text/plain
unnamed ganesh, 2019-09-22.11:56:43 text/plain
See mailing list archives for discussion on individual patches.
Messages
msg21499 (view) Author: ganesh Date: 2019-09-20.18:58:49
Some dependency bumps for 2.14. Some of them merge
cleanly to 2.15 and I'll apply them there, the rest
I'll re-apply by hand.

We still won't support the latest shelly and binary.

I can't bump shelly for the reasons documented
in the patch below nor binary, because darcs 2.14
already indirectly depends on constraints which
doesn't support binary 0.10.

I'll self-accept them as trivial

4 patches for repository /home/ganesh/darcs/branch-2.14-temp:

patch d8d89f7a9d027fdb484f33259f32099f64dc6e69
Author: Ganesh Sittampalam <ganesh@earth.li>
Date:   Fri Sep 20 19:41:31 BST 2019
  * document why we can't bump the shelly dependency

patch 4fe7102bc5f6570267b82f9207f6031bc80e5261
Author: Ganesh Sittampalam <ganesh@earth.li>
Date:   Fri Sep 20 19:43:18 BST 2019
  * support hashable 1.3

patch 2e36442eac494c2322d2f3d9c368f83c37575652
Author: Ganesh Sittampalam <ganesh@earth.li>
Date:   Fri Sep 20 19:43:23 BST 2019
  * support network 3.0 and 3.1

patch 79c3656b9e4590d3166f5080c3b2b2fc90542520
Author: Ganesh Sittampalam <ganesh@earth.li>
Date:   Fri Sep 20 19:44:15 BST 2019
  * support QuickCheck 2.13
Attachments
msg21512 (view) Author: bf Date: 2019-09-21.10:37:55
This is targeted at branch-2.14. I guess it shouldn't stay in state
needs-screening forever... how do we handle that?
msg21515 (view) Author: ganesh Date: 2019-09-21.11:05:03
We don't have a super-clean process, but it's not too bad in practice.

Some of the patches are already in screened, the ones that conflict I will
re-apply by hand and push.
msg21531 (view) Author: ganesh Date: 2019-09-22.11:56:43
Here are the version bumps for screened that I couldn't
just pull directly from 2.14.

I'll leave the QuickCheck change for a bit in case there
are any objections. (2.14 doesn't have that instance so
doesn't have this issue)

2 patches for repository darcs-unstable@darcs.net:screened:

patch e9a3073134dc4c3cf2513fe0145bfb4b29560726
Author: Ganesh Sittampalam <ganesh@earth.li>
Date:   Sun Sep 22 12:10:37 BST 2019
  * support hashable 1.3

patch c16c23d39078febb5a184cb1ed7c909f794e10d8
Author: Ganesh Sittampalam <ganesh@earth.li>
Date:   Sun Sep 22 12:58:24 BST 2019
  * move to QuickCheck 2.13
  
  It defines a Testable Maybe instance we currently have an
  orphan for. Since it works with all versions of GHC we
  support, just switch to it unconditionally to avoid CPP.
Attachments
msg21542 (view) Author: bf Date: 2019-09-23.11:50:08
> I'll leave the QuickCheck change for a bit in case there
> are any objections. (2.14 doesn't have that instance so
> doesn't have this issue)

No objections from my side if it works with ghc-8.2.
History
Date User Action Args
2019-09-20 18:58:50ganeshcreate
2019-09-21 10:37:55bfsetmessages: + msg21512
2019-09-21 11:05:03ganeshsetmessages: + msg21515
2019-09-22 11:56:43ganeshsetfiles: + patch-preview.txt, support-hashable-1_3.dpatch, unnamed
messages: + msg21531
2019-09-23 11:50:08bfsetmessages: + msg21542
2019-09-24 19:33:14ganeshsetstatus: needs-screening -> accepted-pending-tests
2019-09-25 21:05:00ganeshsetstatus: accepted-pending-tests -> accepted