Upstream software project

ghc-lumberjack

Haskell lumberjack library documentation

About ghc-lumberjack

Haskell lumberjack library documentation

This project links 8 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 4 package records; Fedora 44: 4 package records. Catalog coverage diagram, not an application screenshot.ghc-lumberjack: recorded package coverageFedora 434 recordsFedora 444 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ghc-lumberjack
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
fedora-43, fedora-44
License expression
ISC
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

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.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package ghc-lumberjack

    43 (Fedora 43) (Unspecified): Trek through your code forest and make logs

    1.0.3.0-7.fc43: aarch64 x86_64

    Source: ghc-lumberjack

  2. Package ghc-lumberjack-devel

    43 (Fedora 43) (Unspecified): Haskell lumberjack library development files

    1.0.3.0-7.fc43: aarch64 x86_64

    Source: ghc-lumberjack

  3. Package ghc-lumberjack-doc

    43 (Fedora 43) (Unspecified): Haskell lumberjack library documentation

    1.0.3.0-7.fc43: noarch

    Source: ghc-lumberjack

  4. Package ghc-lumberjack-prof

    43 (Fedora 43) (Unspecified): Haskell lumberjack profiling library

    1.0.3.0-7.fc43: aarch64 x86_64

    Source: ghc-lumberjack

Fedora 44

  1. Package ghc-lumberjack

    44 (Fedora 44) (Unspecified): Trek through your code forest and make logs

    1.0.3.0-10.fc44: aarch64 x86_64

    Source: ghc-lumberjack

  2. Package ghc-lumberjack-devel

    44 (Fedora 44) (Unspecified): Haskell lumberjack library development files

    1.0.3.0-10.fc44: aarch64 x86_64

    Source: ghc-lumberjack

  3. Package ghc-lumberjack-doc

    44 (Fedora 44) (Unspecified): Haskell lumberjack library documentation

    1.0.3.0-10.fc44: noarch

    Source: ghc-lumberjack

  4. Package ghc-lumberjack-prof

    44 (Fedora 44) (Unspecified): Haskell lumberjack profiling library

    1.0.3.0-10.fc44: aarch64 x86_64

    Source: ghc-lumberjack

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.