name: htsn
-version: 0.0.1
+version: 0.0.10
cabal-version: >= 1.8
author: Michael Orlitzky
maintainer: Michael Orlitzky <michael@orlitzky.com>
doc/htsnrc.example
doc/man1/htsn.1
doc/init.openrc
+ test/shell/*.test
test/xml/*.xml
synopsis:
Parse XML files from The Sports Network feed.
.
If you specify a file here, logs will be written to it (possibly in
addition to syslog). Can be either a relative or absolute path. It
- will not be auto-rotated; use something log logrotate for that.
+ will not be auto-rotated; use something like logrotate for that.
.
Default: none
.
\--log-level
@
.
- How verbose should the logs be? We log notifications at three levels:
- INFO, WARN, and ERROR. Specify the \"most boring\" level of
+ How verbose should the logs be? We log notifications at four levels:
+ DEBUG, INFO, WARN, and ERROR. Specify the \"most boring\" level of
notifications you would like to receive (in all-caps); more
- interesting notifications will be logged as well.
+ interesting notifications will be logged as well. The debug output is
+ extremely verbose and will not be written to syslog even if you try.
.
Default: INFO
.
.
(Daemon mode only) Create a PID file in the given location. This is
used by the init system on Unix to keep track of the running daemon.
- Its parent directory must be writable by the user/group that we will
- run as!
+ .
+ If necessary, its parent directory will be created with owner/group
+ set to the appropriate user/group, but at most one directory will
+ be created (that is, we won't create an entire directory tree).
.
Default: \/run\/htsn\/htsn.pid
.
.
Any of the command-line options mentioned above can be specified in a
configuration file instead. We first look for \"htsnrc\" in the
- system configuration directory (/etc on Unix). We then look for a file
- named \".htsnrc\" in the user's home directory. The latter will override
+ system configuration directory. We then look for a file named
+ \".htsnrc\" in the user's home directory. The latter will override
the former.
.
+ The user's home directory is simply $HOME on Unix; on Windows it's
+ wherever %APPDATA% points. The system configuration directory
+ is determined by Cabal; the /sysconfdir/ parameter during
+ the \"configure\" step is used.
+ .
The file's syntax is given by examples in the htsnrc.example file
(included with /htsn/).
.
executable htsn
build-depends:
- ansi-terminal == 0.6.*,
- base == 4.*,
+ base >= 4.6 && < 5,
cmdargs >= 0.10.6,
- configurator == 0.2.*,
- directory == 1.2.*,
- filepath == 1.3.*,
- hdaemonize == 0.4.*,
- hslogger == 1.2.*,
- hxt == 9.3.*,
- MissingH == 1.2.*,
- network == 2.4.*,
- tasty == 0.6.*,
- tasty-hunit == 0.4.*,
- transformers == 0.3.*,
- unix == 2.6.*
+ configurator >= 0.2,
+ directory >= 1.2,
+ filepath >= 1.3,
+ hdaemonize >= 0.4,
+ hslogger >= 1.2,
+ htsn-common >= 0.0.2,
+ hxt >= 9.3,
+ MissingH >= 1.2,
+ network >= 2.4 && < 2.6,
+ tasty >= 0.8,
+ tasty-hunit >= 0.8,
+ unix >= 2.6
main-is:
Main.hs
CommandLine
Configuration
ExitCodes
- Logging
+ FeedHosts
OptionalConfiguration
- Terminal
- TSN.FeedHosts
- TSN.Xml
Unix
+ Xml
ghc-options:
-Wall
-fwarn-incomplete-record-updates
-fwarn-monomorphism-restriction
-fwarn-unused-do-bind
- -rtsopts
- -threaded
- -optc-O3
- -optc-march=native
-O2
ghc-prof-options:
-prof
- -auto-all
- -caf-all
+ -fprof-auto
+ -fprof-cafs
hs-source-dirs: src test
main-is: TestSuite.hs
build-depends:
- ansi-terminal == 0.6.*,
- base == 4.*,
+ base >= 4.6 && < 5,
+ cmdargs >= 0.10.6,
+ configurator >= 0.2,
+ directory >= 1.2,
+ filepath >= 1.3,
+ hdaemonize >= 0.4,
+ hslogger >= 1.2,
+ htsn-common >= 0.0.2,
+ hxt >= 9.3,
+ MissingH >= 1.2,
+ network >= 2.4 && < 2.6,
+ tasty >= 0.8,
+ tasty-hunit >= 0.8,
+ unix >= 2.6
+ -- It's not entirely clear to me why I have to reproduce all of this.
+ ghc-options:
+ -Wall
+ -fwarn-hi-shadowing
+ -fwarn-missing-signatures
+ -fwarn-name-shadowing
+ -fwarn-orphans
+ -fwarn-type-defaults
+ -fwarn-tabs
+ -fwarn-incomplete-record-updates
+ -fwarn-monomorphism-restriction
+ -fwarn-unused-do-bind
+ -O2
+
+
+-- These won't work without shelltestrunner installed in your
+-- $PATH. Maybe there is some way to tell Cabal that.
+test-suite shelltests
+ type: exitcode-stdio-1.0
+ hs-source-dirs: src test
+ main-is: ShellTests.hs
+ build-depends:
+ base >= 4.6 && < 5,
cmdargs >= 0.10.6,
- configurator == 0.2.*,
- directory == 1.2.*,
- filepath == 1.3.*,
- hdaemonize == 0.4.*,
- hslogger == 1.2.*,
- hxt == 9.3.*,
- MissingH == 1.2.*,
- network == 2.4.*,
- tasty == 0.6.*,
- tasty-hunit == 0.4.*,
- transformers == 0.3.*,
- unix == 2.6.*
+ configurator >= 0.2,
+ directory >= 1.2,
+ filepath >= 1.3,
+ hdaemonize >= 0.4,
+ hslogger >= 1.2,
+ htsn-common >= 0.0.2,
+ hxt >= 9.3,
+ MissingH >= 1.2,
+ network >= 2.4 && < 2.6,
+ process >= 1.1,
+ tasty >= 0.8,
+ tasty-hunit >= 0.8,
+ unix >= 2.6
-- It's not entirely clear to me why I have to reproduce all of this.
ghc-options:
-fwarn-incomplete-record-updates
-fwarn-monomorphism-restriction
-fwarn-unused-do-bind
- -rtsopts
- -threaded
- -optc-O3
- -optc-march=native
-O2