simonmichael/hledger
1
1
Fork 0
mirror of https://github.com/simonmichael/hledger.git synced 2024-11-08 07:09:28 +03:00
Code Issues Projects Releases Wiki Activity
c1e9ea8fd1
hledger/hledger-lib/package.yaml

155 lines
3.3 KiB
YAML
Raw Normal View History

lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
name: hledger-lib
bump version strings & bounds to 1.5
2017-12-31 21:16:49 +03:00
version: '1.5'
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
synopsis: Core data types, parsers and functionality for the hledger accounting tools
format package descriptions more nicely
2016-08-09 21:27:00 +03:00
description: |
This is a reusable library containing hledger's core functionality.
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
hledger is a cross-platform program for tracking money, time, or
any other commodity, using double-entry accounting and a simple,
editable file format. It is inspired by and largely compatible
with ledger(1). hledger provides command-line, curses and web
interfaces, and aims to be a reliable, practical tool for daily
format package descriptions more nicely
2016-08-09 21:27:00 +03:00
use.
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
category: Finance
Use more accurate license tag in Cabal file.
2017-03-08 11:19:13 +03:00
license: GPL-3
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
author: Simon Michael <simon@joyful.com>
maintainer: Simon Michael <simon@joyful.com>
github: simonmichael/hledger
homepage: http://hledger.org
bug-reports: http://bugs.hledger.org
lib: similar package.yaml whitespace
2017-08-26 02:53:41 +03:00
stability: stable
tested-with: GHC==7.10.3, GHC==8.0.2, GHC==8.2.1
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
extra-source-files:
- CHANGES
- README
lib: similar package.yaml whitespace
2017-08-26 02:53:41 +03:00
reorder yaml files consistently
2016-08-09 21:39:42 +03:00
data-files:
fix data-files paths in yaml/cabal files
2017-12-07 05:45:01 +03:00
- hledger_csv.5
- hledger_csv.txt
- hledger_csv.info
- hledger_journal.5
- hledger_journal.txt
- hledger_journal.info
- hledger_timedot.5
- hledger_timedot.txt
- hledger_timedot.info
- hledger_timeclock.5
- hledger_timeclock.txt
- hledger_timeclock.info
lib: similar package.yaml whitespace
2017-08-26 02:53:41 +03:00
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
dependencies:
set base lower bound to 4.8 to enforce GHC 7.10+ hledger-lib had a valid install plan with GHC 7.8, but requires GHC 7.10 to compile (currently). Require base 4.8+ everywhere so that stack/cabal will enforce a supported GHC version early. Also, bump hledger-ui's "stability" to "stable".
2016-11-17 00:14:02 +03:00
- base >=4.8 && <5
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- base-compat >=0.8.1
remove upper bounds on all but hledger* and base It's rare that my deps break their api or that newer versions must be avoided, and very common that they release new versions which I must tediously and promptly test and release hackage revisions for or risk falling out of stackage. Trying it this way for a bit.
2017-12-31 20:13:50 +03:00
- ansi-terminal >=0.6.2.3
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- array
- blaze-markup >=0.5.1
- bytestring
remove upper bounds on all but hledger* and base It's rare that my deps break their api or that newer versions must be avoided, and very common that they release new versions which I must tediously and promptly test and release hackage revisions for or risk falling out of stackage. Trying it this way for a bit.
2017-12-31 20:13:50 +03:00
- cmdargs >=0.10
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- containers
- csv
- data-default >=0.5
- Decimal
- deepseq
- directory
- filepath
consistent spacing in bounds
2017-12-31 20:05:39 +03:00
- hashtables >=1.2
remove upper bounds on all but hledger* and base It's rare that my deps break their api or that newer versions must be avoided, and very common that they release new versions which I must tediously and promptly test and release hackage revisions for or risk falling out of stackage. Trying it this way for a bit.
2017-12-31 20:13:50 +03:00
- megaparsec >=5.0
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- mtl
- mtl-compat
- old-time
consistent spacing in bounds
2017-12-31 20:05:39 +03:00
- parsec >=3
pkg: rename terminfo flag, drop pretty-show conditionals
2016-08-09 22:16:24 +03:00
- pretty-show >=1.6.4
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- regex-tdfa
- safe >=0.2
lib: fix a deps problem in package.yaml breaking test suite with ghc 8.2
2017-08-26 00:39:35 +03:00
- semigroups
remove upper bounds on all but hledger* and base It's rare that my deps break their api or that newer versions must be avoided, and very common that they release new versions which I must tediously and promptly test and release hackage revisions for or risk falling out of stackage. Trying it this way for a bit.
2017-12-31 20:13:50 +03:00
- split >=0.1
- text >=1.2
lib, cli, ui, web: drop oldtime flag, require time 1.5+ Should be safe to do now, I hope.
2017-08-26 02:56:41 +03:00
- time >=1.5
remove upper bounds on all but hledger* and base It's rare that my deps break their api or that newer versions must be avoided, and very common that they release new versions which I must tediously and promptly test and release hackage revisions for or risk falling out of stackage. Trying it this way for a bit.
2017-12-31 20:13:50 +03:00
- transformers >=0.2
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- uglymemo
remove upper bounds on all but hledger* and base It's rare that my deps break their api or that newer versions must be avoided, and very common that they release new versions which I must tediously and promptly test and release hackage revisions for or risk falling out of stackage. Trying it this way for a bit.
2017-12-31 20:13:50 +03:00
- utf8-string >=0.3.5
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- HUnit
lib: add dependecy on 'extra' package It has a collection of useful list processing functions.
2017-11-29 14:40:40 +03:00
- extra
lib: add a copy of the ledger4 parser This adds some or all of these as new dependencies for hledger-lib: parsers, parsec, attoparsec, trifecta
2016-11-12 21:50:57 +03:00
# for ledger-parse:
consistent spacing in bounds
2017-12-31 20:05:39 +03:00
#- parsers >=0.5
lib: disable WIP ledger4 parser, lighten dependencies
2017-03-30 07:00:16 +03:00
#- system-filepath
consistent spacing in bounds
2017-12-31 20:05:39 +03:00
#- trifecta >=0.91
lib: similar package.yaml whitespace
2017-08-26 02:53:41 +03:00
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
ghc-options:
- -Wall
- -fno-warn-unused-do-bind
- -fno-warn-name-shadowing
- -fno-warn-missing-signatures
- -fno-warn-type-defaults
- -fno-warn-orphans
lib: similar package.yaml whitespace
2017-08-26 02:53:41 +03:00
lib: add a copy of the ledger4 parser This adds some or all of these as new dependencies for hledger-lib: parsers, parsec, attoparsec, trifecta
2016-11-12 21:50:57 +03:00
source-dirs:
lib: disable WIP ledger4 parser, lighten dependencies
2017-03-30 07:00:16 +03:00
#- other/ledger-parse
lib: add a copy of the ledger4 parser This adds some or all of these as new dependencies for hledger-lib: parsers, parsec, attoparsec, trifecta
2016-11-12 21:50:57 +03:00
- .
lib: similar package.yaml whitespace
2017-08-26 02:53:41 +03:00
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
library:
exposed-modules:
- Hledger
- Hledger.Data
- Hledger.Data.Account
- Hledger.Data.AccountName
- Hledger.Data.Amount
- Hledger.Data.Commodity
- Hledger.Data.Dates
- Hledger.Data.Journal
- Hledger.Data.Ledger
Added a simple 'showMarketPrice' function to show market price directives in a journal-compatible way (#505) * added showMarketPrice and Hledger.Data.MarketPrice module * showMarketPrice implemented using showDate * attempted to add tests to Hledger.Data.MarketPrice * moved MarketPrice test to Hledger.Read.JournalReader; fixed documentation on MarketPrice; added MarketPrice module to package.yaml
2017-02-04 05:20:00 +03:00
- Hledger.Data.MarketPrice
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- Hledger.Data.Period
- Hledger.Data.StringFormat
- Hledger.Data.Posting
- Hledger.Data.RawOptions
- Hledger.Data.Timeclock
- Hledger.Data.Transaction
Make hledger-rewrite tool suitable for re-factoring original journals (#490) * cli: fix bug in pivot for postings without tag Without this fix for postings without tag query checked effective account which is always empty text (""). * rewrite: inherit dates, change application order For budgeting it is important to inherit actual date of posting if it differs from date of transaction. These dates will be added as a separate line of comment. More natural order of rewrites is when result of first defined one is available for all next rewrites. * rewrite: factor out Hledger.Data.AutoTransaction * rewrite: add diff output With this option you can modify your original files without loosing inter-transaction comments etc. I.e. you can run: hledger-rewrite --diff Agency \ --add-posting 'Expenses:Taxes *0.17' \ | patch As result multiple files should be updated. Also it is nice to review your changes using colordiff instead of patch. * lib: track source lines range for journal * doc: auto entries and diff output for rewrite
2017-01-20 18:33:24 +03:00
- Hledger.Data.AutoTransaction
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- Hledger.Data.Types
- Hledger.Query
- Hledger.Read
- Hledger.Read.Common
- Hledger.Read.CsvReader
- Hledger.Read.JournalReader
lib: disable WIP ledger4 parser, lighten dependencies
2017-03-30 07:00:16 +03:00
# - Hledger.Read.LedgerReader
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- Hledger.Read.TimedotReader
- Hledger.Read.TimeclockReader
- Hledger.Reports
- Hledger.Reports.ReportOptions
- Hledger.Reports.BalanceHistoryReport
- Hledger.Reports.BalanceReport
- Hledger.Reports.EntriesReport
- Hledger.Reports.MultiBalanceReports
- Hledger.Reports.PostingsReport
- Hledger.Reports.TransactionsReports
- Hledger.Utils
lib: begin supporting colour Add some basic helpers for working with ANSI colour codes, and make strWidth and the various string layout functions aware of them.
2017-04-26 04:27:25 +03:00
- Hledger.Utils.Color
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
- Hledger.Utils.Debug
- Hledger.Utils.Parse
- Hledger.Utils.Regex
- Hledger.Utils.String
- Hledger.Utils.Test
- Hledger.Utils.Text
- Hledger.Utils.Tree
- Hledger.Utils.UTF8IOCompat
add support for megaparsec 6 (fixes #594) Older megaparsec is still supported. Also cleans up our custom parser types, and some text (un)packing is done in different places (possible performance impact).
2017-07-27 14:59:55 +03:00
- Text.Megaparsec.Compat
lib: disable WIP ledger4 parser, lighten dependencies
2017-03-30 07:00:16 +03:00
# other-modules:
# - Ledger.Parser.Text
lib: similar package.yaml whitespace
2017-08-26 02:53:41 +03:00
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
tests:
doctests:
main: doctests.hs
source-dirs: tests
dependencies:
- doctest >=0.8
pkg: clean up deps slightly
2016-08-09 21:52:15 +03:00
- Glob >=0.7
lib, cli, web, api: use hpack (package.yaml) for all packages at last #371 Generated package.yaml files from the old cabal files with hpack-convert, removed some problematic blank lines manually, regenerated the cabal files from the package.yaml files with hpack. Tests pass, looks like all the info is still there. This means that from now on, we don't edit cabal files directly. We edit the less verbose package.yaml files. stack will update the cabal files automatically (or non-stack users can use hpack). The changes to both are committed, as we still want to provide the cabal files to downloaders.
2016-08-09 17:24:41 +03:00
hunittests:
main: hunittests.hs
source-dirs: tests
dependencies:
- hledger-lib
- test-framework
- test-framework-hunit
Reference in New Issue Copy Permalink