Convention for naming manual pages: .l vs .1

[wohler at sri-spam.UUCP]

In article <3403 at cbosgd.ATT.COM> kww at cbosgd.UUCP (Kevin W. Wall) writes:
>When posting sources to net.sources, mod.sources, etc., please do NOT use
>the suffix .l (i.e., the lowercase letter L) for the names of manual pages.
>This suffix is "reserved" for LEX files ("reserved" as in "conventional"),
>and also quite often breaks makefiles.
...
>	File name		Meaning
>	----------	---------------------------
>	prog.1		Standard (non-local) command called "prog".
>	prog.1l		Local command called "prog".

kevin,

  even 4.xBSD make interprets the '.l' suffix as a file that contains
  lex source.

  another "standard" which makes life easier (ever see Sun's tmac.an
  file?) is to just append the '.1' suffix to ANY section one command,
  whether it be local (l), new (n), or whatever IN THE SOURCE.  then,
  have your "make install" portion of the makefile copy the man page
  to the desired location in /usr/man with the correct suffix.  for
  instance:

-----
MAN        = foo.1
MANDIR	   = /usr/man/man
MANSECT	   = n

install:
	cp ${MAN} ${MANDIR}n/`basename ${MAN} .1`.${MANSECT}
-----

  when distributing source, don't make any assumptions about where
  people might like to put your sources (ie. with man page file names
  like foo.1l).  let the Makefile contain that information.

							--bw