Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <034601c19899$fc1c35d0$0200a8c0@lifelesswks> From: "Robert Collins" To: , References: <3C3B34DC DOT 5674 DOT 3155089 AT localhost> Subject: Re: Updated Gnu tools manpages, maybe you'd like to know? ('gnumaniak') Date: Wed, 9 Jan 2002 10:12:44 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 08 Jan 2002 23:12:46.0176 (UTC) FILETIME=[FB9B4600:01C19899] ----- Original Message ----- From: "Soren Andersen" > On 8 Jan 2002 at 22:03, Robert Collins wrote: > > > Given that info documentation can be converted to manpages, I see little > > reason to maintain man pages separately. > > Over the course of using cygwin in the past, `info' wouldn't always work > for me. Maybe some flag or .rc file hadn't been set, whatever. It does work > now. Yes, I know. Remember that I'm writing my emails in the context of what has been fixed. info is a known previous issue, and the packaging guidelines explicitly mention handling of info pages. > Just because something "can" (in abstract principle) be done, doesn't > always mean *everyone* currently "can" or (more to the point) "knows how". > That's the whole point of binary distros of any[open-source]thing, is it > not? So that people can focus on what they are most interested in > developing or using? Do you want a philsophical discussion on the english language? I presume you simply missed the point of my comment. Packages such as bash (picking one at random) have 'up to date' manpages. I believe (haven't checked the Makefile) they achieve this by virtue of converting their info documentation to man pages, not by manually updating the man pages. So it doesn't matter if everyone can. It matters if the package maintainers can. It doesn't matter if only the upstream package developers know how, their makefiles do it for the package maintainers (most of the time). > general policy we could be informed about, that would hold true most of the > time, regarding how out-of-date the manpages might be? Someone reading this > might know. There is no policy regarding manpages for packages in the cygwin net distribution at this point in time. Common sense prevails. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/