This is the mail archive of the
java-patches@sources.redhat.com
mailing list for the Java project.
Re: Patch: generate texinfo documentation
- To: Bryce McKinlay <bryce at albatross dot co dot nz>
- Subject: Re: Patch: generate texinfo documentation
- From: Tom Tromey <tromey at redhat dot com>
- Date: 08 Jan 2001 12:55:45 -0700
- Cc: green at cygnus dot com, java-patches at sources dot redhat dot com
- References: <200101080022.QAA16140@makita.cygnus.com> <3A593356.196D8DC9@albatross.co.nz>
- Reply-To: tromey at redhat dot com
>>>>> "Bryce" == Bryce McKinlay <bryce@albatross.co.nz> writes:
Bryce> Do we really want these in gcj? Arn't they just bulking up the
Bryce> distribution with duplicated information? If people do find
Bryce> them useful, wouldn't it be better to set up a server side
Bryce> script to periodically regenerate them against the cvs sources,
Bryce> and put them in a separate archive (libgcj-docs-xxyyzz.tar.gz
Bryce> or something?). It might also be good to generate html versions
Bryce> and have them accessible online.
We should definitely have them online.
One problem with including them in the distribution is that according
to the GNU standards we should also include .info files. That would
add even more bulk.
Bryce> On a related note, I'm quite keen to write a real .texi manual
Bryce> for gcj that incorporates a lot of the information thats
Bryce> currently scattered around the website, etc (but then I've been
Bryce> saying this for a while ;-). IIRC you were working on something
Bryce> like this a while ago... was there ever any progress? We should
Bryce> get this done before the 3.0 release.
I agree, this is very important. I have time to work on gcj projects
right now. Anthony, could you send me what you have? I think this is
the most important thing to do right now. I'll work on it.
Tom