- Next message: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Previous message: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- In reply to: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Next in thread: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Reply: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
On Jan 2, 2007, at 10:03 PM, Eric S. Raymond wrote:
> Brian Barrett <brbarret_at_[hidden]>:
>> Thank you. These changes have been committed (with some small
>> changes) into our subversion repository and will be part of the next
>> LAM release.
>
> I'll have a few more coming. Your project has man pages in places
> I did not originally check.
>
> The immediate purpose behind these is to clean everything up so it can
> be automatically lifted to XML-DocBook by a tool I wrote for the
> purpose. That in turn is a means to supporting automatic generatiion
> of high-quality HTML that distro integrators can use to replace
> man-page trees.
>
> To this end, I hope your "some small changes" won't involve adding
> low-level troff requests back in -- .br, .ti, and .in are especially
> problematic.
No, the small changes are because Red Hat's RPM renames some of the
man pages in that RPM and we have updated some of the pages since the
release included with Fedora.
I was playing with running your tool on our man pages. It seemed to
not be too concerned with some of the issues you brought up,
particularly the use of angle brackets in the synopsis section. Is
there a way to have it complain about those issues? I ask in part
because I'd like to integrate the tool into our testing process for
both LAM/MPI and Open MPI. While LAM's man pages are pretty static,
Open MPI is under active development and our man pages change
frequently. It would be nice to have a sanity check that we aren't
generating bad manpages that troff lets "slip by".
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
- Next message: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Previous message: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- In reply to: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Next in thread: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
- Reply: Eric S. Raymond: "Re: problems in lamboot.1, lamexec.1, lammsg.1, lamrun.1, lamtask.1, lamshrink.1, lamd.1"
|
