Date: Tue, 8 Mar 2005 15:31:26 +0100 From: Jeremie Le Hen <jeremie@le-hen.org> To: Maxime Henrion <mux@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: gcc(1) manpage (was: cvs commit: src/sys/kern kern_sig.c) Message-ID: <20050308143126.GN94451@obiwan.tataz.chchile.org> In-Reply-To: <20050308132228.GD31320@elvis.mu.org> References: <200503020915.28512.jhb@FreeBSD.org> <4226446B.7020406@freebsd.org> <61ac46c154aa515a692308440dd1141d@FreeBSD.org> <422710DD.1070203@freebsd.org> <422719E0.10703@samsco.org> <20050307195156.GA18850@dragon.nuxi.com> <422CBDEE.7020307@samsco.org> <20050307211942.GA37106@ns1.xcllnt.net> <20050308131613.GA812@galgenberg.net> <20050308132228.GD31320@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > 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. Juste my 2 cents :-). Regards, [1] ports/textproc/info2man [2] http://jeremie.le-hen.org/~tataz/gcc_info2man/gcc.1 -- Jeremie Le Hen jeremie at le-hen dot org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050308143126.GN94451>