haskell-lumberjack 1.0.3.0-1 source package in Ubuntu

Changelog

haskell-lumberjack (1.0.3.0-1) unstable; urgency=medium

  * Declare compliance with Debian policy 4.6.2
  * New upstream release

 -- Ilias Tsitsimpis <email address hidden>  Sun, 03 Sep 2023 14:25:31 +0300

Upload details

Uploaded by:
Debian Haskell Group
Uploaded to:
Sid
Original maintainer:
Debian Haskell Group
Architectures:
any all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc
Noble release universe misc

Downloads

File Size SHA-256 Checksum
haskell-lumberjack_1.0.3.0-1.dsc 2.7 KiB df8bcf3fac3ec0adada61ef1a4675e9724f7bd080b4f5df16ee8204231800dd2
haskell-lumberjack_1.0.3.0.orig.tar.gz 10.5 KiB 18458e37aeca5f2e294c0341662bc58dafe447e40e580f5666889043d87e4415
haskell-lumberjack_1.0.3.0-1.debian.tar.xz 2.5 KiB 5a06acdcecebe018861283d3bf716f7422072208b6affe4121c5a413e60598c2

No changes file available.

Binary packages built by this source

libghc-lumberjack-dev: Trek through your code forest and make logs

 This is a logging facility. Yes, there are many, and this is the one
 with a beard, wearing flannel and boots, that gets the job done. It's
 not the fanciest, it doesn't have a cargo-van full of features. This
 logger is designed to be straightforward to use, provide a good set of
 standard features, and be useable across a broad set of code.
 .
  * Logging itself is a monadic activity. This activity is most often
 performed in a monad stack with a MonadIO context to allow
 writing to files.
 .
  * The specific logging action implementations are managed separately
 from the actions of logging messages in the target code. This
 allows logging to be configurable and the manner of logging to
 be specified at startup time without requiring changes in the
 code from which log messages are being generated.
 .
  * The logging implementation code can use contravariant functors to
 adjust existing logging.
 .
  * Main code will typically retrieve the logging actions from a Reader
 context in your monad stack. That said, Log actions are not tied
 to an enclosing Monad. There are helpers to support a Monad which
 can store Log actions, but Log actions can also be explicitly
 passed and used.
 .
  * The prettyprinter package is used for formatting.
 .
 This package provides a library for the Haskell programming language.
 See http://www.haskell.org/ for more information on Haskell.

libghc-lumberjack-doc: Trek through your code forest and make logs; documentation

 This is a logging facility. Yes, there are many, and this is the one
 with a beard, wearing flannel and boots, that gets the job done. It's
 not the fanciest, it doesn't have a cargo-van full of features. This
 logger is designed to be straightforward to use, provide a good set of
 standard features, and be useable across a broad set of code.
 .
  * Logging itself is a monadic activity. This activity is most often
 performed in a monad stack with a MonadIO context to allow
 writing to files.
 .
  * The specific logging action implementations are managed separately
 from the actions of logging messages in the target code. This
 allows logging to be configurable and the manner of logging to
 be specified at startup time without requiring changes in the
 code from which log messages are being generated.
 .
  * The logging implementation code can use contravariant functors to
 adjust existing logging.
 .
  * Main code will typically retrieve the logging actions from a Reader
 context in your monad stack. That said, Log actions are not tied
 to an enclosing Monad. There are helpers to support a Monad which
 can store Log actions, but Log actions can also be explicitly
 passed and used.
 .
  * The prettyprinter package is used for formatting.
 .
 This package provides the documentation for a library for the Haskell
 programming language.
 See http://www.haskell.org/ for more information on Haskell.

libghc-lumberjack-prof: Trek through your code forest and make logs; profiling libraries

 This is a logging facility. Yes, there are many, and this is the one
 with a beard, wearing flannel and boots, that gets the job done. It's
 not the fanciest, it doesn't have a cargo-van full of features. This
 logger is designed to be straightforward to use, provide a good set of
 standard features, and be useable across a broad set of code.
 .
  * Logging itself is a monadic activity. This activity is most often
 performed in a monad stack with a MonadIO context to allow
 writing to files.
 .
  * The specific logging action implementations are managed separately
 from the actions of logging messages in the target code. This
 allows logging to be configurable and the manner of logging to
 be specified at startup time without requiring changes in the
 code from which log messages are being generated.
 .
  * The logging implementation code can use contravariant functors to
 adjust existing logging.
 .
  * Main code will typically retrieve the logging actions from a Reader
 context in your monad stack. That said, Log actions are not tied
 to an enclosing Monad. There are helpers to support a Monad which
 can store Log actions, but Log actions can also be explicitly
 passed and used.
 .
  * The prettyprinter package is used for formatting.
 .
 This package provides a library for the Haskell programming language, compiled
 for profiling. See http://www.haskell.org/ for more information on Haskell.