cvs commit: ports/www Makefile ports/www/p5-FCGI-ProcManager Makefile distinfo pkg-descr pkg-plist

[Anton Berezin]

On Mon, Dec 31, 2007 at 12:28:05AM +0000, Martin Wilke wrote:
> miwi        2007-12-31 00:28:05 UTC
> 
>   FreeBSD ports repository
> 
>   Modified files:
>     www                  Makefile 
>   Added files:
>     www/p5-FCGI-ProcManager Makefile distinfo pkg-descr pkg-plist 
>   Log:
>   FCGI::ProcManager is used to serve as a FastCGI process manager.  By
>   re-implementing it in perl, developers can more finely tune performance in
>   their web applications, and can take advantage of copy-on-write semantics
>   prevalent in UNIX kernel process management.  The process manager should
>   be invoked before the caller''s request loop
>   
>   WWW:    http://search.cpan.org/dist/FCGI-ProcManager/
>   
>   PR:             ports/119009
>   Submitted by:   Peter <peter at vereshagin.org>
>   
>   Revision  Changes    Path
>   1.1933    +1 -0      ports/www/Makefile
>   1.1       +22 -0     ports/www/p5-FCGI-ProcManager/Makefile (new)
>   1.1       +3 -0      ports/www/p5-FCGI-ProcManager/distinfo (new)
>   1.1       +7 -0      ports/www/p5-FCGI-ProcManager/pkg-descr (new)
>   1.1       +5 -0      ports/www/p5-FCGI-ProcManager/pkg-plist (new)

Why this ever got added?  There is an identical port
www/p5-FastCGI-ProcManager.  Now we are getting PRs with updates to this one
(see 119300), where PR authors *complain* about someone updating "the wrong
port", refering to gabor's update of www/p5-FastCGI-ProcManager recently...

What a mess.  I'd like committers adding new ports to be a *bit* more
careful and verify that the port is indeed *new*.

It can be argued that the "new" name is better that the "old" one, but this
is an entirely separate can of worm.  Grrrr.

Cheers,
\Anton.
-- 
We're going for 'working' here. 'clean' is for people with skills...
-- Flemming Jacobsen