Having a separate hashed-storage package to install is causing lots of
confusion, particularly now that there's a different hashed-storage-0.5.11
on hackage. For now Guillaume and I think it's easiest to maintain this
directly inside the darcs cabal file.
2 patches for repository darcs-unstable@darcs.net:screened:
Tue Apr 22 07:09:02 BST 2014 Ganesh Sittampalam <ganesh@earth.li>
* drop NoMonomorphismRestriction from hashed-storage
Tue Apr 22 18:55:40 BST 2014 Ganesh Sittampalam <ganesh@earth.li>
* dumb merge of hashed-storage.cabal etc into darcs.cabal
Lots of opportunities for further cleanups but this should come as close
as possible to replicating the behaviour of the separate cabal file.
Getting started on cleaning up after the hashed-storage.cabal merge
1 patch for repository darcs-unstable@darcs.net:screened:
Wed Apr 23 07:20:48 BST 2014 Ganesh Sittampalam <ganesh@earth.li>
* switch hashed-storage-test to be a proper test harness
This required fixing Setup.lhs to pass custom CPP defines to test suites,
as the standard Cabal library function for setting them up only applies
them to libraries and executables.