haskell-lumberjack 1.0.1.0-2build1 source package in Ubuntu
Changelog
haskell-lumberjack (1.0.1.0-2build1) lunar; urgency=medium * Rebuild against new GHC ABI. -- Gianfranco Costamagna <email address hidden> Sat, 10 Dec 2022 11:35:17 +0100
Upload details
- Uploaded by:
- Gianfranco Costamagna
- Uploaded to:
- Lunar
- Original maintainer:
- Debian Haskell Group
- Architectures:
- any all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Mantic | release | universe | misc | |
| Lunar | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| haskell-lumberjack_1.0.1.0.orig.tar.gz | 10.4 KiB | 702ae4fd9e6d32bfce2ae84e6cda2b67723a46cf192b857fa3d8b271a651df77 |
| haskell-lumberjack_1.0.1.0-2build1.debian.tar.xz | 2.5 KiB | b6716cd4728218d9e3874cb4134aa17c0a134cb418f5d764a590c2e3219273c1 |
| haskell-lumberjack_1.0.1.0-2build1.dsc | 2.7 KiB | 5444a4cc381e8b9398eeb925b14ec6056b1e82ca46a67562a8921d55f20c44c2 |
Available diffs
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.
