ports/126932: gapcmon option in sysutils/apcupsd conflicts with sysutils/gapcmon

[Jason E. Hale]

>Number:         126932
>Category:       ports
>Synopsis:       gapcmon option in sysutils/apcupsd conflicts with sysutils/gapcmon
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 29 04:00:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Jason E. Hale
>Release:        FreeBSD 7.0-STABLE i386
>Organization:
none 
>Environment:
System: FreeBSD 7.0-STABLE #0: Wed Aug 6 23:19:34 EDT 2008 i386
	
>Description:
In sysutils/apcupsd, a GAPCMON OPTION was added which conflicts with
sysutils/gapcmon.  This is the same program and installs in the same
location.  The sysutils/gapcmon port has been in place before gapcmon was
bundled with apcupsd.
	
>How-To-Repeat:
Install sysutils/gapcmon and sysutils/apcupsd with the GAPCMON OPTION enabled;
they will install conflicting files.
	
>Fix:
There are several things that can be done:
1. CONFLICTS obviously will not work since gapcmon requires apcupsd.
2. Change the GAPCMON OPTION in sysutils/apcupsd to simply depend on the 
   sysutils/gapcmon port as a RUN_DEPENDS.
3. Remove the GAPCMON OPTION from sysutils/apcupsd.
4. Remove the sysutils/gapcmon port which would still require CONFLICTS.

I am the maintainer of sysutils/gapcmon and I favor option #2 since the separate
gapcmon project is updated more often than the one bundled with apcupsd.  It
would also still give the user the option of installing the GUI.
sysutils/gapcmon does not depend on sysutils/apcupsd, so there wouldn't be a
"chicken-egg" problem.
	

>Release-Note:
>Audit-Trail:
>Unformatted: