This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: cygwin-doc ready for upload
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 15 Apr 2002 23:14:30 -0400
- Subject: Re: cygwin-doc ready for upload
- References: <20020416030008.58433.qmail@web20002.mail.yahoo.com>
- Reply-to: cygwin-apps at cygwin dot com
On Mon, Apr 15, 2002 at 08:00:08PM -0700, Joshua Daniel Franklin wrote:
>>I just checked the discussion about this, and you asked if someone was
>>already maintaining newlib-man. I don't think I ever answered but the
>>answer is "no". It looks like the man pages aren't even generated by
>>newlib anymore. Instead there is a big info file generated by 'make
>>info'.
>>
>>Any chance that this could be incorpoated into your distribution? The
>>sources are already part of the cygwin package so there isn't any need
>>to include them.
>
>OK, it sounds like I should:
>1) incorporate newlib-man-20001118 into cygwin-doc, maybe after a
>little sed that would put a "This doc is no longer being maintained;
>try info"
But, where would the user find the info file? It isn't in any distribution
yet.
Alternatively, you could just include the current newlib info files in the
package.
>2) work on something to break the current newlib texinfo into man pages
There are packages to do this. Possibly gcc uses one already.
>Either way, I'd rather go ahead with the cygwin-doc as-is and put it on
>my documentation todo list.
I don't want to be pushy but I would really prefer that you incorporate
the newlib stuff via either 1) or 2) (2 preferred). I foresee confusion
otherwise.
cgf