This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: [patch] generate man pages for classpath tools
- From: Tom Tromey <tromey at redhat dot com>
- To: Matthias Klose <doko at cs dot tu-berlin dot de>
- Cc: classpath-patches at gnu dot org, java at gcc dot gnu dot org
- Date: 16 Feb 2007 15:30:35 -0700
- Subject: Re: [patch] generate man pages for classpath tools
- References: <17876.60724.466685.919534@gargle.gargle.HOWL>
- Reply-to: tromey at redhat dot com
>>>>> "Matthias" == Matthias Klose <doko@cs.tu-berlin.de> writes:
Matthias> The GCC tools generate man pages for all commands, this
Matthias> patch does the same for the tools installed by classpath.
Matthias> The patch is for classpath HEAD.
Please check this in. This is excellent.
I think we ought to rename the Classpath .texi and .info files to be
more Classpath-specific. The /usr/share/info "namespace" is flat
after all. So instead of "tools.info" I would suggest
"cp-tools.info".
Matthias> * doc/gappletviewer.1, doc/gjar.1, doc/gjarsigner.1, doc/gjavah.1,
Matthias> doc/gkeytool.1, doc/gnative2ascii.1, doc/gorbd.1, doc/grmid.1,
Matthias> doc/grmiregistry.1, doc/gserialver.1, doc/gtnameserv.1: Generate.
I saw these in the patch. Classpath generally does not check in
generated files (with the occasionally troublesome exception of the
JNI headers). So, don't put them in the Classpath tree. For GCC, do
whatever the rest of GCC does.
Tom