aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Gröber <dxld@darkboxed.org>2017-09-26 13:17:04 +0200
committerDaniel Gröber <dxld@darkboxed.org>2017-09-26 13:17:04 +0200
commit0e5511a9d58f47edb3790236391d75279553504e (patch)
treeb7b5908cc2e18d111b180b4943e152ef5844171d
parentad7638c770aec55f8305433414b7644bc941cb7c (diff)
Reflow package description in cabal file for 80cols
[ci skip]
-rw-r--r--cabal-helper.cabal37
1 files changed, 20 insertions, 17 deletions
diff --git a/cabal-helper.cabal b/cabal-helper.cabal
index 236a4bb..92570b9 100644
--- a/cabal-helper.cabal
+++ b/cabal-helper.cabal
@@ -1,26 +1,29 @@
name: cabal-helper
version: 0.8.0.0
-synopsis: Simple interface to some of Cabal's configuration state, mainly used by ghc-mod
+synopsis:
+ Simple interface to some of Cabal's configuration state, mainly used by ghc-mod
description:
- Cabal's little helper provides access to build information gathered by @cabal@
- when configuring a project. Specifically we're interested in retrieving enough
- information to bring up a compiler session, using the GHC API, which is similar
- to running @cabal repl@ in a project.
+ Cabal's little helper provides access to build information gathered by
+ @cabal@ when configuring a project. Specifically we're interested in
+ retrieving enough information to bring up a compiler session, using the GHC
+ API, which is similar to running @cabal repl@ in a project.
.
- While simple in principle this is complicated by the fact that the information
- Cabal writes to disk is in an unstable format and only really accessible through
- the Cabal API itself.
+ While simple in principle this is complicated by the fact that the
+ information Cabal writes to disk is in an unstable format and only really
+ accessible through the Cabal API itself.
.
- Since we do not want to bind the user of a development tool which utilises this
- library to a specific version of Cabal we compile the code which interfaces with
- the Cabal library's API on the user's machine, at runtime, against whichever
- version of Cabal was used to write the on disk information for a given project.
+ Since we do not want to bind the user of a development tool which utilises
+ this library to a specific version of Cabal we compile the code which
+ interfaces with the Cabal library's API on the user's machine, at runtime,
+ against whichever version of Cabal was used to write the on disk information
+ for a given project.
.
- If this version of Cabal is not available on the users machine anymore, which is
- fairly likely since cabal-install is usually linked statically, we have support
- for compiling the Cabal library also. In this case the library is installed into
- a private, isolated, package database in @$XDG_CACHE_DIR/cabal-helper@ so as to
- not interfere with the user's package database.
+ If this version of Cabal is not available on the users machine anymore,
+ which is fairly likely since cabal-install is usually linked statically, we
+ have support for compiling the Cabal library also. In this case the library
+ is installed into a private, isolated, package database in
+ @$XDG_CACHE_DIR/cabal-helper@ so as to not interfere with the user's package
+ database.
license: AGPL-3
license-file: LICENSE
license-files: LICENSE LICENSE.cabal-dependency-licenses