Re: Packages with un usable documentation
On Sun, Apr 04, 2004 at 03:33:51PM +0200, Otto Wyss wrote:
> To solve my mkinitrd problem I searched for solutions. Each time someone
> has run into my problem he was asked if module-init-tools are installed
> and each time it was answered yes. Unfortunately also each time no
> further action is mentioned.
>
> I looked into module-init-tools to find out what's doing. First I tried
> "man module-init-tools" which didn't work. Second I looked into
> "/usr/share/doc/module-init-tools" just to discover there is just
> useless common facts. Third I started dselect and read the package
> description which didn't help further.
>
> Shouldn't packages which don't provide any useable information in one of
> these three locations marked as broken with a grave bug?
If you file a grave bug about this I shall downgrade it immediately!
> IMO the best way is to have a "man <packagename>" which simply gives
> links and hints to where to look for more information, a man file with
> just a "SEE ALSO" section. Each package which doesn't do this should get
> an important bug.
dlocate -man
> IMO a must in any case is a "/usr/share/doc/<packagename>/README.debian"
> which lists all possible "man ..." of this package. Each package which
> doesn't do this should get an serious bug.
Serious bugs will likewise be downgraded. Please don't inflate bug
severities; it's extremely rude.
http://release.debian.org/sarge_rc_policy.txt
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: