🚀 go-pugleaf

A few ideas for additional doodads in autoconf (I haven't gotten
around to adding them myself yet, just having obtained autoconf about
an hour ago, but thought I'd mention them to see if anyone has any
opinions...):

1)  It'd be nice if there were some configuration for building man
    pages instead of just copying them, so that SysV systems that have
    a /usr/catman instead of /usr/man can have man pages compiled
    correctly.

    I use something like this in my makefiles:

    mandir = /usr/local/man
    manext = 1

    #makeman = 
    #makeman = | eqn | tbl | nroff -man | col -x
    makeman = | groff -Tlatin1 -man -et | col -x

    #packman = :
    #packman = compress
    packman = pack

    install.man:
            -cat foo.man $(makeman) > $(mandir)/foo.$(manext);\
                $(packman) $(mandir)/foo.$(manext)

    Then on systems with /usr/man you use the empty version of
    $(makeman).  You could figure out whether or not to pack/compress
    the man page by looking to see if the normal man pages are packed
    (foo.1.z) or compressed (foo.1.Z).

2)  I'd like to see _sys_siglist[] and variants handled: I've seen the
    following variants:

        _sys_siglist[]
        sys_siglist[]
        const char *dg_strsignal()

    Perhaps the configuration could defined a macro, say STRSIGNAL(),
    which takes a signal number as an argument and returns a char*
    which is a text name for the signal, or something like
    "<unavailable>" if there is no siglist or the signal is not a
    member of the list.

                                                                paul
-----
 ------------------------------------------------------------------
| Paul D. Smith                          |    paul_smith@dg.com    |
| Data General Corp.                     | pds@lemming.webo.dg.com |
| Network Systems Development Division   |                         |
| Open Network Systems Development       |   "Pretty Damn S..."    |
 ------------------------------------------------------------------