Herbert Valerio Riedel
Herbert Valerio Riedel
The API changes from `time-1.5` to `time-1.6` don't affect HsOpenSSL afaics. I've already performed a `.cabal`-edit on Hackage to this effect: https://hackage.haskell.org/package/HsOpenSSL-0.11.1.1/revisions/, so there's no need to upload a new...
The API for integer-gmp has significantly changed with `integer-gmp-1.0.0.0` See https://hackage.haskell.org/package/integer-gmp-1.0.0.0/candidate/docs/GHC-Integer-GMP-Internals.html for details
It would be convenient to be able to specify the default sandbox location (which currently seems hard-coded to `./cabal-dev`) via an environment variable. The `-s`/`--sandbox=DIR` option should have always precedence...
Currently, I use `select` as in e.g. ``` haskell coms =. lo') &&. (ComArtNumField
due to the use of `ConstraintKinds` which are only available starting with GHC 7.4 (maybe add a `base >= 4.5` constraint to future releases)
so that `cabal get -s categories` doesn't have to fail with ``` cabal: Package categories-1.0.6 does not have any source repositories. ```
Does the API allow to create horizontal bar graphs (rather than vertical bars, and if so, how?); random example: 
This automatically sets the meta-data in the generated src tarballs more accurately and reduces the risk of this package's meta-data bitrotting over time. Addresses #5 See also https://docs.haskellstack.org/en/stable/yaml_configuration/#pvp-bounds
The `cursor.cabal` is lacking any meaningful bounds, i.e. ``` build-depends: base (Char -> Validation) -> Validation | 48 | , decorateList (rebuildListCursor lc) $ \c -> | ^^^^^^^^^^^^ ``` or...
The general recommendation seems to be to place pragmas after the entity they apply to. But in case of the `{-# MINIMAL #-}` pragma, I think the following works best...