I do not know texinfo, and looking at that example (it's actually,
gcc/java/gcj.texi) has frightened me. A shorter example would probably
help much more, but really, I was only looking for a man page as I was
trying to see what all the programs on my system were for. Learning
texinfo right now is just not something I can get enthusiastic about
(although maybe if I can find an entertaining manual...).
I do however have a slight (very slight) understanding of creating
manpages in troff (looking at this first frightened me even more, but I
was unfortunate enough to learn to read it long ago).
Attached is a manpage taken from the glibc package for glibcbug and
modified for gccbug.
As I cannot find documentation on gccbug, the options and their
descriptions were created from trying to figure out what the script is
doing. I am not a {scripter, programmer, writer}. I may have
misinterpreted or incorrectly described something.
You may want to s/gccbug/gccbug-3.2, or you may want to rename
gccbug-3.2 to gccbug. The latter makes more sense to me as the only
other gccbug is in usr/lib/gcc-snapshot/bin/gccbug, so I wrote the man
page without "-3.2". But hey, there are reasons I'm not a package
maintainer. :)
Also attached is a patch to get gccbug to use /usr/bin/sensible-editor
instead of vi.
Thanks for the work you put into these packages, it's really appreciated
by many!
-
Omniflux
Matthias Klose writes:
> Omniflux writes:
> > Package: gcc-3.2
> > Version: 1:3.2.3-0pre2
> > Severity: minor
> >
> > gccbug-3.2 has no manpage.
>
> would you mind writing one? texinfo format would be preferred. See
> gcc/doc/gcj.texi for an example (in the gcc-3.2 source).
Attachment:
gccbug.in.patch
Description: Binary data
Attachment:
gccbug.1
Description: Binary data