Cabal revisions of gargoyle-0.1.2.0
Hackage metadata revisions edit the .cabal file after upload; each diff below is one revision.
revision 1
-name: gargoyle-version: 0.1.2.0-license: BSD3-license-file: LICENSE-author: Obsidian Systems LLC-maintainer: maintainer@obsidian.systems-copyright: Copyright (C) Obsidian Systems LLC 2017-category: System-build-type: Simple-cabal-version: >=1.10-synopsis: Automatically spin up and spin down local daemons-description:- Gargoyle is a framework for managing daemons from Haskell. In the current release the only requirement is that the daemon be able to communicate over a Unix domain socket. See <https://hackage.haskell.org/package/gargoyle-postgresql gargoyle-postgresql> for a fully worked out example.- .- To use Gargoyle the client must:- .- 1. Define a value of the 'Gargoyle' type which specifies how to administer the daemon.- 2. Create an executable whose `main` is 'gargoyleMain'. The name of this executable should match the executable name specified in the '_gargoyle_exec' field of the 'Gargoyle'.- 3. The client will run their code with 'withGargoyle' to gain access to the daemon.--extra-source-files:- ChangeLog.md- README.md--tested-with: GHC ==8.6.5 || ==8.8.4 || ==8.10.7 || ==9.0.2--library- exposed-modules: Gargoyle- ghc-options: -Wall- ghc-prof-options: -fprof-auto-exported- build-depends:- base >=4.12.0 && <4.17- , directory >=1.3.3 && <1.4- , filelock >=0.1.1 && <0.2- , filepath >=1.4.2 && <1.5- , network >=2.6.0 && <3.2- , process >=1.5.0 && <1.7- , unix >=2.7.2 && <2.8-- hs-source-dirs: src- default-language: Haskell2010+name: gargoyle +version: 0.1.2.0 +x-revision: 1 +license: BSD3 +license-file: LICENSE +author: Obsidian Systems LLC +maintainer: maintainer@obsidian.systems +copyright: Copyright (C) Obsidian Systems LLC 2017 +category: System +build-type: Simple +cabal-version: >=1.10 +synopsis: Automatically spin up and spin down local daemons +description: + Gargoyle is a framework for managing daemons from Haskell. In the current release the only requirement is that the daemon be able to communicate over a Unix domain socket. See <https://hackage.haskell.org/package/gargoyle-postgresql gargoyle-postgresql> for a fully worked out example. + . + To use Gargoyle the client must: + . + 1. Define a value of the 'Gargoyle' type which specifies how to administer the daemon. + 2. Create an executable whose `main` is 'gargoyleMain'. The name of this executable should match the executable name specified in the '_gargoyle_exec' field of the 'Gargoyle'. + 3. The client will run their code with 'withGargoyle' to gain access to the daemon. + +extra-source-files: + ChangeLog.md + README.md + +tested-with: GHC ==8.6.5 || ==8.8.4 || ==8.10.7 || ==9.0.2 + +library + exposed-modules: Gargoyle + ghc-options: -Wall + ghc-prof-options: -fprof-auto-exported + build-depends: + base >=4.12.0 && <4.20 + , directory >=1.3.3 && <1.4 + , filelock >=0.1.1 && <0.2 + , filepath >=1.4.2 && <1.5 + , network >=2.6.0 && <3.2 + , process >=1.5.0 && <1.7 + , unix >=2.7.2 && <2.9 + + hs-source-dirs: src + default-language: Haskell2010