Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <20020416172519.13860.qmail@web20002.mail.yahoo.com> Date: Tue, 16 Apr 2002 10:25:19 -0700 (PDT) From: Joshua Daniel Franklin Subject: Re: cygwin-doc ready for upload To: cygwin-apps AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii > >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. > Ah, didn't think of this. I just assumed it was, somewhere. I think including the current newlib info will be a nice gesture, yes. > >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 downloaded the gcc source to check for this before checking http://cygwin.com/packages/ which told me that texi2man is in...GNU units.?? That's what I get for not installing all the packages, I guess. Looks like just a perl script 'units' includes for completeness. I might put it in cygwin-doc as well. > 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. Well, yes, but the confusion happens either way... OK, expect a cygwin-doc w/ newlib docs (info and man) shortly. This will mean replacing the current newlib-man with an empty package, too, I believe. Maybe one with a postinstall scripts to remove the deprecated pages. __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/