ports/119413: Double port/naming inconsistence

Peter peter at vereshagin.org
Mon Jan 7 10:30:01 UTC 2008


>Number:         119413
>Category:       ports
>Synopsis:       Double port/naming inconsistence
>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:   Mon Jan 07 10:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Peter
>Release:        5.4-STABLE #13
>Organization:
Private
>Environment:
FreeBSD screwed.box 5.4-STABLE FreeBSD 5.4-STABLE #13: Thu Oct 19 10:13:53 SAMST 2006     toor at screwed.box:/usr/local/src/sys/i386/compile/OPER  i386
>Description:
I submitted the port, the www/p5-FCGI-ProcManager.
But there already exists the www/p5-FastCGI-ProcManager.
Think we need to avoid such misunderstandings cause there exist the www/p5-FCGI-Async.
I simply did not found the p5-FastCGI-ProcManager cause i was looking index for p5-FCGI, for the FCGI perl namespace.
So i do submit the www/p5-FCGI-Spawn next, but:
a. need to know what port to depend on, the p5-FCGI-ProcManager or p5-FastCGI-ProcManager
b. need the common naming convention to name the port p5-FCGI-Spawn or the p5-FastCGI-Spawn.
>How-To-Repeat:
make search ProcManager
>Fix:


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



More information about the freebsd-ports-bugs mailing list