[ 14:39 feld  ]

• 411079 comms/Makefile
• 411079 comms/qpage
• 411079 comms/qpage/Makefile
• 411079 comms/qpage/files/patch-config.c
• 411079 comms/qpage/files/patch-config.h.in
• 411079 comms/qpage/files/patch-config.input
• 411079 comms/qpage/files/patch-ixo.c
• 411079 comms/qpage/files/patch-qpage.man
• 411079 comms/qpage/files/patch-srvrsnpp.c
• 411079 comms/qpage/files/patch-util.c

comms/qpage: Resurrect port

- New MASTER_SITE
- New MAINTAINER
- Change to USES=tar:Z
- Regenerate patches

PR:		206321

[ 12:38 marino  ]

• 363056 UPDATING
• 363056 comms/qpage/Makefile
• 363056 comms/qpage/files/patch-config.h.in
• 363056 comms/qpage/files/patch-config.input
• 363056 comms/qpage/files/patch-qpage.man
• 363056 comms/qpage/pkg-plist

Stage comms/qpage

The PR wasn't quite right with regards to stage support, so I had to modify
it further.  The post-install configure file handling was focused on the
wrong file.  I updated the default name of the qpage configure file in
order to use the @sample keyword.  I added an entry in UPDATING to let
users know they may need to move an existing configure file accordingly.

PR:		192120
Submitted by:	maintainer (Jeff Blank)
Changes by:	marino

[ 08:48 edwin  ]

• 1.22 comms/qpage/Makefile
• 1.1 comms/qpage/files/patch-config.h.in
• 1.1 comms/qpage/files/patch-config.input
• 1.1 comms/qpage/files/patch-qpage.man

Nitpicks for the comms/qpage port

        The comms/qpage port has a few minor problems.  A default installation
gives
        the following errors when the /usr/local/etc/rc.d/qpage.sh script is
        execute:

            qpage[68438]: cannot open /etc/qpage.cf: No such file or directory
            qpage[68438]: cannot access LockDir(/var/spool/lock): Permission
denied
            qpage[68438]: cannot access QueueDir(/var/spool/qpage): No such file
or directory
            qpage[68438]: cannot chdir to QueueDir(/var/spool/qpage): No such
file or directory

        In short:

        1) qpage looks for its configuration file in /etc instead of
/usr/local/etc
        2) It setuid()'s to a user (daemon) without permission to access
/var/spool/lock
        but does not document this anywhere outside of the source.
        3) It's queue directory is not created by installing the port.

PR:             ports/48059
Submitted by:   Kirk Strauser <kirk@strauser.com>