Created attachment 152249 [details] waf port shar The Waf framework The Waf framework is somewhat different from traditional build systems in the sense that it does not provide support for a specific language. Rather, the focus is to support the major usecases encountered when working on a software project. As such, it is essentially a library of components that are suitable for use in a build system, with an emphasis on extensibility. Although the default distribution contains various plugins for several programming languages and different tools (c, d, ocaml, java, etc), it is by no means a frozen product. Creating new extensions is both a standard and a recommended practice. WWW: https://code.google.com/p/waf/
Created attachment 152252 [details] waf port shar - fixed
Thanks for your submission Radim, Note: This port has previously existed in the ports tree under devel/py-waf, before being removed in 2012. See bug 160910 for detail. Can you provide a compelling case for it to be reintroduced given that the authors of waf discourage including it system packaging?
Created attachment 152256 [details] waf port shar - added LICENSE
This port is needed for creating scripts, i need it for regenerating ./waf script after patching during build process. It might be used by security/hotssh port as build dependency instead of shipping waf diff. Its targeted at developers, not as system wide tool like scons.
Created attachment 152259 [details] added no_arch
Created attachment 152260 [details] poudriere build log
Radim, I would propose that if this port is accepted, that it ought to be named py-waf. Can you update the attached patch to suit please. Thanks!
Also see: * https://code.google.com/p/waf/wiki/FAQ#Why_is_packaging_of_waf_in_distributions_discouraged? * https://en.wikipedia.org/wiki/Waf#License
I havent noticed that documentation has different license, i will remove it from package, its not needed anyway. You want this port named with prefix py${PYTHON_VERSION}?
The license of the documentation is not an issue for us. I referenced the link to evidence the fact that the upstream authors made changes intentionally to avoid their system being offered in system package repositories. Regarding the naming prefix, using ${PYTHON_VERSION is unnecessary. PKGNAMEPREFIX=${PYTHON_PKGNAMEPREFIX} is what's used. That is: - The directory name should be devel/py-waf - The PORTNAME should be waf - PKGNAMEPREFIX should be ${PYTHON_PKGNAMEPREFIX
Created attachment 152353 [details] port renamed to py-waf
Update Summary to reflect new consensus
Thanks guys. Any news about this? Is there still any interest to add this port? If so please update the patch for new upstream, as GOOGLE_CODE is dead, and latest version is 1.9.6: https://github.com/waf-project/waf
I'm gonna go ahead and close this. Please reopen or file a new report if you want to continue reviving this port, with a corrected master site.