Add Binary instances for many types
So we can use them in binary cache files. Also relax version constraints on binary to work with binary-0.5.*, which requires that we expose Distribution.Compat.Binary from Cabal. D.Compat.Binary provides the Gerics support that we need to be able to derive instances when using binary-0.5. It's useful to be able to use binary-0.5 since that's the version bundled with older ghc versions.
Showing
- Cabal/Cabal.cabal 1 addition, 1 deletionCabal/Cabal.cabal
- cabal-install/Distribution/Client/BuildReports/Types.hs 7 additions, 1 deletioncabal-install/Distribution/Client/BuildReports/Types.hs
- cabal-install/Distribution/Client/ComponentDeps.hs 9 additions, 2 deletionscabal-install/Distribution/Client/ComponentDeps.hs
- cabal-install/Distribution/Client/Dependency/Types.hs 17 additions, 4 deletionscabal-install/Distribution/Client/Dependency/Types.hs
- cabal-install/Distribution/Client/InstallPlan.hs 7 additions, 0 deletionscabal-install/Distribution/Client/InstallPlan.hs
- cabal-install/Distribution/Client/PackageIndex.hs 7 additions, 1 deletioncabal-install/Distribution/Client/PackageIndex.hs
- cabal-install/Distribution/Client/Setup.hs 7 additions, 0 deletionscabal-install/Distribution/Client/Setup.hs
- cabal-install/Distribution/Client/Targets.hs 11 additions, 3 deletionscabal-install/Distribution/Client/Targets.hs
- cabal-install/Distribution/Client/Types.hs 59 additions, 8 deletionscabal-install/Distribution/Client/Types.hs
- cabal-install/cabal-install.cabal 9 additions, 0 deletionscabal-install/cabal-install.cabal
Loading
Please register or sign in to comment