ports/160910: devel/py-waf: request for marking it DEPRECATED

[Ruslan Mahmatkhanov]

>Number:         160910
>Category:       ports
>Synopsis:       devel/py-waf: request for marking it DEPRECATED
>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:   Thu Sep 22 14:10:06 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Ruslan Mahmatkhanov
>Release:        9.0-BETA2
>Organization:
>Environment:
9.0-BETA2 i386
>Description:
Our devel/py-waf port is outdated. Latest release is on 1.6.7. Author discourages system-wide waf installation [1] and most of linuces already removed it long time ago from their reposes. 
The point is, that waf-script that bundled with some distributed software, is all-sufficient (it's actually packed waf framework) and if we will try to build this software with some system-wide installed waf, we can get all sorts of configure/build problems. If you check existing ports in the tree (14 at all), that use waf for installing, noone use devel/py-waf - they all just do "./waf configure|build|install" in WRKSRC. 
So i believe that this port is quite useless and should be removed to not confuse our users. Since no port depend on this, it's safe to do so. 

If some developer will decide to use waf to install his software, he manually download waf http://waf.googlecode.com/files/waf-1.6.7 and bundle it with his software, as stated in Waf Book [2].

[1] http://code.google.com/p/waf/wiki/FAQ#Why_is_packaging_of_waf_in_distributions_discouraged?

[2] http://docs.waf.googlecode.com/git/book_16/single.html#_obtaining_the_waf_file
>How-To-Repeat:

>Fix:


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