summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRuss Allbery <rra@cpan.org>2022-01-15 17:19:47 -0800
committerRuss Allbery <rra@cpan.org>2022-01-15 17:19:47 -0800
commit1f37c387a11c4e22bf127b777bcf391af8b68471 (patch)
tree7ed3a5a064a927a27fc4013db32eed9158fe43c9
parent6f52c93f689a654e759a4216cb0a911d07640f72 (diff)
Update the package description
* Update the package description to reflect that it is now also a static web site generator.
-rw-r--r--debian/changelog2
-rw-r--r--debian/control15
2 files changed, 10 insertions, 7 deletions
diff --git a/debian/changelog b/debian/changelog
index b428b77..1a99061 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,6 +6,8 @@ docknot (6.01-1) UNRELEASED; urgency=medium
- Avoid changing working directories in docknot spin.
- Fix requirement for package metadata when running docknot spin.
- Don't overwrite output files if docknot generate fails.
+ * Update the package description to reflect that it is now also a static
+ web site generator.
-- Russ Allbery <rra@debian.org> Sat, 15 Jan 2022 17:15:09 -0800
diff --git a/debian/control b/debian/control
index 5fff4cb..8d9fe50 100644
--- a/debian/control
+++ b/debian/control
@@ -67,10 +67,11 @@ Depends:
pkwalify,
${misc:Depends},
${perl:Depends},
-Description: Manage software documentation and distributions
- DocKnot is a system for generating 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. DocKnot also automates generating distribution
- tarballs for software packages.
+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.