Bug 197122 - [NEW PORT] devel/py-waf: Meta build system
Summary: [NEW PORT] devel/py-waf: Meta build system
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: VK
URL: https://en.wikipedia.org/wiki/Waf#Lic...
Keywords: needs-patch, needs-qa, patch
Depends on:
Blocks:
 
Reported: 2015-01-27 07:26 UTC by Radim Kolar
Modified: 2017-01-12 16:48 UTC (History)
1 user (show)

See Also:


Attachments
waf port shar (12.40 KB, text/plain)
2015-01-27 07:26 UTC, Radim Kolar
no flags Details
waf port shar - fixed (14.72 KB, text/plain)
2015-01-27 07:38 UTC, Radim Kolar
no flags Details
waf port shar - added LICENSE (14.74 KB, text/plain)
2015-01-27 10:22 UTC, Radim Kolar
no flags Details
added no_arch (14.76 KB, text/plain)
2015-01-27 16:28 UTC, Radim Kolar
no flags Details
poudriere build log (21.72 KB, text/plain)
2015-01-27 16:37 UTC, Radim Kolar
no flags Details
port renamed to py-waf (14.84 KB, text/plain)
2015-01-29 20:50 UTC, Radim Kolar
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Radim Kolar 2015-01-27 07:26:21 UTC
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/
Comment 1 Radim Kolar 2015-01-27 07:38:46 UTC
Created attachment 152252 [details]
waf port shar - fixed
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2015-01-27 09:00:42 UTC
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?
Comment 3 Radim Kolar 2015-01-27 10:22:51 UTC
Created attachment 152256 [details]
waf port shar - added LICENSE
Comment 4 Radim Kolar 2015-01-27 10:33:42 UTC
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.
Comment 5 Radim Kolar 2015-01-27 16:28:51 UTC
Created attachment 152259 [details]
added no_arch
Comment 6 Radim Kolar 2015-01-27 16:37:20 UTC
Created attachment 152260 [details]
poudriere build log
Comment 7 Kubilay Kocak freebsd_committer freebsd_triage 2015-01-28 02:35:10 UTC
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!
Comment 9 Radim Kolar 2015-01-28 06:45:16 UTC
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}?
Comment 10 Kubilay Kocak freebsd_committer freebsd_triage 2015-01-28 10:34:12 UTC
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
Comment 11 Radim Kolar 2015-01-29 20:50:26 UTC
Created attachment 152353 [details]
port renamed to py-waf
Comment 12 Mark Linimon freebsd_committer freebsd_triage 2015-01-29 21:23:12 UTC
Update Summary to reflect new consensus
Comment 13 VK freebsd_triage 2016-12-12 01:59:44 UTC
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
Comment 14 VK freebsd_triage 2017-01-12 16:48:23 UTC
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.