Reid Kaufmann wrote: > Ok, I've seen this come up a few times, so I think it deserves it's own email > topic rather than getting piggy-backed on code reviews that perhaps not > everyone is looking at. I don't know if I can answer the question > definitively, but I'm sure someone on the forum can... >> 2. usr/src/lib/libmhash/install-sfw This still includes (see item 2 below) >> .. 'MANSCRIPT=../sunman-stability' Is this required? >> > I think in most cases people (myself included) are including this because the > Sun internal instructions for package porting, titled > Package_Delivery_Project, lists sunman-stability in section 3.4 as one of the > needed files: > > * sunman-stability (usr/src/cmd/expect/sunman-stability) (see Man Pages > below) ... > > *Man Pages* If your package does not come with a man page, you will need to > create one. The fastest way to create a new man page is to find a man page > format you like and edit it as needed to document your package. If you do > create a new man page, the sunman-stability file is not needed. > * nroff man page information > * man page sections > * man page development automation (not needed for simple man pages) > * For testing, add your man page path to MANPATH (ie. > MANPATH=/test/man/man1:$MANPATH). It normally needs to be in the man1 > directory. > > So, according to this text, most ports are going to use this. Is this > correct, or has it been obsoleted? >
It has not been obsoleted. Most ports are going to use the sunman-stability file to update the man pages with the interface stability information. But, if you write your own man page, then you can include the stability information in the man page directly, so you don't need the sunman-stability file. Does this answer your question? Should the man page guidelines in the wiki be rewritten? If so, let me know how. Cheers, Jim
