Package: libghc-tasty-doc (1.4.2.3-1)
Haskell testing framework; documentation
Package information
- Homepage
- [https://github.com/UnkindPartition/tasty]
- License
- Desconocido: no consta en la fuente indexada
- Mantenedor del paquete downstream
- Debian Haskell Grouppkg-haskell-maintainers@lists.alioth.debian.org
- Paquete fuente
- [haskell-tasty]
- Software project
- [haskell-tasty]
Versions and downloads for libghc-tasty-doc
| Version / release | Architecture / repository | Package size | Installed size | Files | Publisher repository artifact |
|---|---|---|---|---|---|
| 1.4.2.3-1bookworm / main | allDebian 12 · main · amd64 | 180 KiB | 2.8 MiB | list of files | libghc-tasty-doc_1.4.2.3-1_all.deb |
| 1.4.2.3-1bookworm / main | allDebian 12 · main · arm64 | 180 KiB | 2.8 MiB | list of files | libghc-tasty-doc_1.4.2.3-1_all.deb |
About these downloads
Cada fila es metadato del índice de paquetes para una versión, arquitectura, suite y repositorio. Nombres, URL y tamaños vienen de la fuente; un enlace es un punto de descarga que puede cambiar, no una redistribución de OpenFactory.
Other packages built from haskell-tasty
- libghc-tasty-dev
Haskell testing framework
- libghc-tasty-prof
Haskell testing framework; profiling libraries
Dependencies and recommendations for libghc-tasty-doc
View 9 package relationships
dep: [sgml-base] (>= 1.28)
SGML infrastructure and SGML catalog file support
dep: haddock-interface-38
Package not available
rec: [ghc-doc]
Documentation for the Glasgow Haskell Compilation system
rec: [libghc-ansi-terminal-doc]
Simple ANSI terminal support, with Windows compatibility; documentation
rec: [libghc-optparse-applicative-doc]
utilities and combinators for parsing command-line options; documentation
rec: [libghc-tagged-doc]
newtype wrappers for phantom types; documentation
rec: [libghc-tasty-dev]
Haskell testing framework
rec: [libjs-mathjax]
JavaScript display engine for LaTeX and MathML
sug: [libghc-tasty-prof]
Haskell testing framework; profiling libraries
Rutas de archivos del paquete (0)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
No package-associated file paths were observed for the displayed build metadata.
Field source: Debian 12 (Bookworm) main amd64
