On Mon, 2003-01-13 at 11:33, Sebastian Rittau wrote:
> > The documentation of a program should be included in the binary
> > package, unless it is large, in which case a separate -doc package is
> > acceptable. Mention the -doc package in Debian.README. Install
> > documentation in /usr/share/doc/package/, and include doc-base and
> > .dhelp files.
> This doesn't belong into the GNOME policy, since it's already part of
> the main Debian policy.
Good point, removed.
> > The documentation of a library should be generated with a tool such as
> > gtk-doc or doxygen at package build time, and either included in the
> > -dev package if it is small, or in a separate -doc package. DEFINE
> > SMALL.
> Just say "reasonably small" and leave the decision at the maintainer's
> discretion. We don't need to be super-exact.
Done.
> > When gconftool supports it, the prerm script should also un-apply the
> > schemas. This is currently unimplemented however.
> Shouldn't this only be done when a package is purged?
Yes, it should. Of course this is all pipedream as the gconftool
command doesn't support this yet :)
> > Always remember to update the config.{guess|sub} files at build-time,
> > see the documentation in /usr/share/doc/autotool-dev for
> > details. Don't forget to build-depend on autotools-dev.
> Don't put this into the GNOME policy. This belongs into the Best
> Packaging Practices document.
Removed.
Thanks for the feedback.
Ross
--
Ross Burton mail: ross@burtonini.com
jabber: ross@nerdfest.org
www: http://www.burtonini.com./
PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
Attachment:
signature.asc
Description: This is a digitally signed message part