[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ next ]
doc-base
Manual
Make the install-docs
code more manageable (split into modules,
etc.)
Add support for merging doc-base files with the same Document-Ids
in order to allow two or more binary packages provide the same documentation,
but in different formats. install-docs
should dynamically
generate appropriate files somewhere under /var/lib/doc-base
directory.
Internationalisation and po-debconf support. Unfortunately this would require
merging Abstract and Title fields into one
Description field. See Bug#171363
, Bug#171375
, and Bug#171378
.
Introduce some new fields, like Package (Bug#71955
), or SortSkip
(Bug#187590
).
Redesigning sections hierarchy, see Bug#109431
.
Policy: document the doc-base
document registration file format
separately (or SUBDOC it) as a proposed Debian documentation system policy.
Policy: define a first-cut standard as the document hierarchy.
Documentation update: show clean and minimal use of install-docs
from maintainer script.
It is extremely difficult to deal coherently with a misnamed control
file, or a mismatch between a control file and the document field. This hit me
in the transition between doc-base
0.4 to 0.5 (in 0.4 I had added,
in a file install-docs-man, a document ID named install-doc-man). Something
needs to be done about that.
Determine a cleaner way to manage the various little files such as
.dhelp
and doc-base
status files. This also involves
behaviour on remove or purge of the doc-base
packages. I believe
derived files such as .dhelp
will eventually go away, since
packages should understand the doc-base
document registration
control file format directly.
Automated format conversion, including user preferences. (For example, convert texinfo source to GNU info or PostScript, optionally compress or remove HTML manuals which are also available in GNU info format, etc. etc.)
[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ next ]
Debian doc-base
Manual
schwarz@debian.org
aph@debian.org
robert@debian.org