1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77
|
Source: docknot
Section: text
Priority: optional
Build-Depends:
debhelper-compat (= 13),
dh-sequence-zz-debputy,
git,
libcapture-tiny-perl,
libfile-basedir-perl,
libfile-copy-recursive-perl,
libfile-sharedir-perl,
libgit-repository-perl,
libimage-size-perl,
libio-compress-lzma-perl,
libio-compress-perl,
libipc-run-perl,
libipc-system-simple-perl,
libjson-maybexs-perl,
liblist-someutils-perl,
libmodule-build-perl,
libpath-iterator-rule-perl,
libpath-tiny-perl,
libperl6-slurp-perl,
libpod-thread-perl (>= 3.01),
libsort-versions-perl,
libtemplate-perl,
libtest-minimumversion-perl,
libtest-pod-coverage-perl,
libtest-pod-perl,
libtest-strict-perl,
libtest-synopsis-perl,
libtimedate-perl,
libyaml-libyaml-perl,
pandoc,
perl,
pkwalify,
Rules-Requires-Root: no
Testsuite: autopkgtest-pkg-perl
Maintainer: Russ Allbery <rra@debian.org>
Standards-Version: 4.7.0
Homepage: https://www.eyrie.org/~eagle/software/docknot/
Vcs-Git: https://salsa.debian.org/rra/docknot.git
Vcs-Browser: https://salsa.debian.org/rra/docknot
X-Style: black
Package: docknot
Architecture: all
Multi-Arch: foreign
Depends:
libfile-basedir-perl,
libfile-sharedir-perl,
libgit-repository-perl,
libimage-size-perl,
libio-compress-lzma-perl,
libio-compress-perl,
libipc-run-perl,
libipc-system-simple-perl,
libjson-maybexs-perl,
liblist-someutils-perl,
libpath-iterator-rule-perl,
libpath-tiny-perl,
libperl6-slurp-perl,
libpod-thread-perl (>= 3.01),
libsort-versions-perl,
libtemplate-perl,
libtimedate-perl,
libyaml-libyaml-perl,
pandoc,
pkwalify,
Description: Static web site and documentation generator
DocKnot is a static web site generator built around a macro language
called thread, with special support for managing software releases. In
addition to building a web site, it can generate distribution tarballs
and consistent human-readable software package documentation from a YAML
metadata file and templates. The goal is to generate both web pages and
distributed documentation files (such as README) from the same source,
using templates for consistency across multiple packages.
|