From owner-freebsd-current@FreeBSD.ORG Tue Mar 8 17:17:58 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7273B16A4CE for ; Tue, 8 Mar 2005 17:17:58 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C82943D53 for ; Tue, 8 Mar 2005 17:17:57 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])j28HHavT001222 for ; Tue, 8 Mar 2005 19:17:36 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) j28G3KdN027417 for ; Tue, 8 Mar 2005 18:03:21 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)j28G0c2j020695; Tue, 8 Mar 2005 18:00:38 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Tue, 8 Mar 2005 18:00:38 +0200 From: Giorgos Keramidas To: Jeremie Le Hen Message-ID: <20050308160038.GA20539@orion.daedalusnetworks.priv> References: <20050308152658.GP94451@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050308152658.GP94451@obiwan.tataz.chchile.org> cc: freebsd-current@freebsd.org Subject: Re: gcc(1) manpage (was: cvs commit: src/sys/kern kern_sig.c) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2005 17:17:58 -0000 On 2005-03-08 16:26, Jeremie Le Hen wrote: >> This version number in the gcc(1) manpage is really the least of the >> problems... The GCC guys don't maintain the manpage anymore, as they >> prefer the info page to document things now. The gcc(1) manpage hasn't >> been updated since _long_. In short, it's not only a matter of getting >> the latest manpage from the GCC project, it's a matter of synchronizing >> this manpage with the (huge) GCC info page and it's a significant job. > > I would take advantage of this thread to ask what people think about > converting gcc(1) info page to a manual page. Of course, this manual > page wouldn't be very academic but IMHO, it would keep the Unix > tradition of having a single manual page containing all informations > about the software. > > It appears there is a tool called info2man [1] : this is a Perl script > that first use info2pod and then pod2man. I agree this is ugly, but > modulo some tweaks, the result seems to be quite readable [2] as a > manual page. David O'Brien has posted a copy of the gcc.1 manpage to be, which has been generated by Pod::Man. Converting this to groff_mdoc is a huge job that I haven't managed to complete yet, even though a few months have passed since I got the message from David. The main problem with this conversion is that I have relatively "high" standards of what the mdoc text should look like, in order to be a BSD manpage. Keeping the standards of the rest of the manpages, as I understand these style/standard guidelines by osmosis (i.e. by looking at the work of Ruslan Ermilov), and having as much of the Texinfo documentation for GCC in one place is a "significant job" as it was said above. One that I am not sure I can manage at my spare time between ${REAL_JOB} stuff. Having said that, I think that a real manpage for GCC would be great! - Giorgos