Date: Tue, 7 Aug 2001 18:04:16 +0930 From: Greg Lehey <grog@FreeBSD.org> To: Warner Losh <imp@harmony.village.org> Cc: Sheldon Hearn <sheldonh@starjuice.net>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, doc@FreeBSD.org Subject: Re: Which OS does a man page come from? (was: cvs commit: src/bi Message-ID: <20010807180416.N1565@wantadilla.lemis.com> In-Reply-To: <200108070829.f778TI113023@harmony.village.org>; from imp@harmony.village.org on Tue, Aug 07, 2001 at 02:29:18AM -0600 References: <29772.997172442@axl.seasidesoftware.co.za> <200108070829.f778TI113023@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 7 August 2001 at 2:29:18 -0600, Warner Losh wrote:
> In message <29772.997172442@axl.seasidesoftware.co.za> Sheldon Hearn writes:
>>>> As I said: we add the .Os and .Dd when installing.
>>>
>>> How is that different than just copying the mandoc macros that were
>>> used to build the man pages from the {cd, network, wherever} you got
>>> the man page sources from?
>>
>> Um, Warner, the point is that right now, if Greg copies an installed
>> _source_ manual page from a FreeBSD system, he gets an empty Os macro:
>>
>> .Os
>>
>> If we do as he suggests, he'll get a populated Os macro:
>>
>> .Os FreeBSD 4.5
>
> I understand that. My point is why not pull the macros used to create
> the man pages from the same place you pulled the man pages. Eg, snag
> /usr/share/tmac at the same time you snagged the man page and setenv
> GROFF_TMAC_PATH to be where you stashed it. I don't see how this is
> different than grabbing old Makefiles and having them produce
> different results on new machine or machines with different kinds of
> make...
It's not the way man(1) works. It takes the macros from the same
place for all man pages.
>>> Adding the .Os and .Dd at install time seems ugly to me.
>>
>> Why? It's just a little Makefile magic. We don't actually add the
>> macro, just an argument, and only in the case where there are no
>> arguments, e.g.
>>
>> s/^\.Os$/.Os FreeBSD 4.5/g
>
> Because it is another target? You'd have foo.5 which would somehow
> get generated from foo.5 which seems gross to me from a make point of
> view. I guess I don't see how that's transparently done in the build
> process.
Well, no, just put it into the man page install target. Currently the
pages get gzipped into /usr/share/man; this would just add a sed pipe.
All we need is to change the man page install target; a SMOP.
Greg
--
See complete headers for address and phone numbers
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010807180416.N1565>