leaky 0.2.1.0 → 0.2.1.1
raw patch · 2 files changed
+56/−27 lines, 2 filesdep ~seqaid
Dependency ranges changed: seqaid
Files
- changelog.txt +7/−2
- leaky.cabal +49/−25
changelog.txt view
@@ -1,13 +1,18 @@ +0.2.1.0 -> 0.2.1.1+ - non-manual USE_CPPHS flag added (also in seqaid and in deepseq-bounded)+ so that client build system can decide whether cpp is available, or+ it needs to install and use cpphs+ 0.2.0.1 -> 0.2.1.0- - realised I should be using Manual: True in all my .cabal flags,+ - realised I should be using "manual:true" in all my .cabal flags, or else the constraint solver is free to toggle them!! 0.2.0.0 -> 0.2.0.1 - added a note in the .cabal description field, about the rogue build failure report -0.1.7.0 -> 0.2.0.0+** 0.1.7.0 -> 0.2.0.0 - deepseq-bounded had a major version bump - fixed cpphs missing dependency for seqaid (also affects this package) - more...
leaky.cabal view
@@ -1,6 +1,6 @@ name: leaky-version: 0.2.1.0+version: 0.2.1.1 synopsis: Robust space leak, and its strictification license: BSD3 license-file: LICENSE@@ -10,12 +10,14 @@ bug-reports: http://fremissant.net/leaky/trac ---bug-reports: Andrew Seniuk <rasfar@gmail.com> category: Testing+--hackage-tags: leak, space, strictness, forcing, diagnostic, remedial, auto-instrumentation, instrumentation, tools, bsd3, program build-type: Simple stability: experimental-cabal-version: >=1.16+cabal-version: >=1.18 -- However, seqaid requires GHC>=7.8. --+-- [Later: I presume this GHC/cabal issue has been resolved by now.] -- As for 7.10.1-rc1, latest cabal-install seemingly -- cannot interoperate with it; but you can compile -- leaky-min.hs at least, which still leaks -O2.@@ -33,7 +35,7 @@ . Please share your comments on this <http://www.reddit.com/r/haskell/comments/2pscxh/ann_deepseqbounded_seqaid_leaky/ reddit> discussion. -- .--- NOTE: Ignore the anonymous rogue failed build report below (at least, it appeared on all versions I uploaded so far). If you examine the log it's clear that the problem is theirs, and nothing to do with this package or its dependencies. It's a shame this is so prominently displayed and impossible to remedy, it makes unbroken packages seem broken to visitors, and it exerts negative pressure on the use of cpphs (since one can make this rogue report go away by pretending cpphs never existed and depending on the ubiquity of a system-wide cpp).+-- NOTE: /Ignore the anonymous rogue failed build report below. If you examine the log it's clear that the problem is theirs, and nothing to do with this package or its dependencies. It's a shame this is so prominently displayed and impossible to remedy, it makes unbroken packages seem broken to visitors, and it exerts negative pressure on the use of cpphs (since one can make this rogue report go away by pretending cpphs never existed and depending on the ubiquity of a system-wide cpp)./ extra-source-files: @@ -152,9 +154,16 @@ -- Sadly, not. -- See bottom of this file for the meanings of the values. -executable leaky+-- This does indeed work for me (it is auto-toggled when cpphs is unavailable).+-- Default to False, since it seems more likely there's a native cpp, than+-- that a cpphs installation works smoothly.+Flag USE_CPPHS+ Description: Non-manual flag to allow the build system to try cpphs first, and if that fails, then to try system-wide cpp (typically GNU). I've actually toggled the default, so the build system will try for a system-wide cpp first, and failing that, will try to use cpphs, installing it if necessary. I prefer cpp. I am not getting my most invaluable -Wundef option with cpphs using -optP-Wundef -optP--cpp in my ghc-options. Does cpphs implement it? Not sure...+ Default: False+--Default: True+ Manual: False - build-tools: cpphs+executable leaky main-is: leaky.hs --main-is: leaky-min.hs@@ -164,11 +173,22 @@ Types_no_SOP , Types_explicit_SOP + -- this is the first time I've tried to use a "condition" with build-tools+ -- and it's a bit hard to test whether it's working...+ if flag(USE_CPPHS)+ build-tools: cpphs+ build-depends:- base == 4.*- , cpphs > 1.14- , random == 1.1+ base == 4.*+ , random == 1.1 + -- We don't really depend on the cpphs /library/, but installing+ -- the library also installs the cpphs executable, so in case+ -- build-tools doesn't nab it, this ought to!+ if flag(USE_CPPHS)+ build-depends:+ cpphs > 1.14+ ---------- BEGIN SEQAID-SPECIFIC -- PART 1 of 2 ---------- -- User would need to add these deps themselves to their project .cabal.@@ -178,26 +198,27 @@ build-depends: - deepseq-bounded == 0.6.* || == 0.7.*- , deepseq-generics == 0.1.*- , generics-sop == 0.1.*- , template-haskell--- , template-haskell == 2.9.*+ deepseq-bounded == 0.6.* || == 0.7.*+ , deepseq-generics == 0.1.*+ , generics-sop == 0.1.*+ , template-haskell+-- , template-haskell == 2.9.* - -- XXX this is no good !! (co-evolving packages)- -- I guess the best is to leave it unconstrained?...- , seqaid == 0.2.1.0--- , seqaid == 0.2.*- -- Hopefully this will simply install the latest one,- -- which ought to be fine:--- , seqaid+ -- XXX this is no good !! (co-evolving packages)+ -- I guess the best is to leave it unconstrained?...+-- , seqaid == 0.2.1.0+ , seqaid == 0.2.1.*+-- , seqaid == 0.2.*+ -- Hopefully this will simply install the latest one,+ -- which ought to be fine:+-- , seqaid if flag(OMNITYPIC) build-depends:- -- first needed by seqaidpp with the omnitypic blanket:- ghc-prim--- ghc-prim <= 0.3.1.0---- , integer-gmp+ -- first needed by seqaidpp with the omnitypic blanket:+ ghc-prim+-- ghc-prim <= 0.3.1.0+--- , integer-gmp ---------- END SEQAID-SPECIFIC -- PART 1 of 2 ---------- @@ -208,7 +229,10 @@ if flag(PROFILE) ghc-options: -fprof-auto -auto-all -caf-all - ghc-options: -pgmPcpphs -optP--cpp+ if flag(USE_CPPHS)+ ghc-options: -pgmPcpphs -optP--cpp+--else+-- ghc-options: -cpp ---------- BEGIN SEQAID-SPECIFIC -- PART 2 of 2 ----------