Package: wnpp Severity: wishlist Owner: Walter Landry <wlan...@caltech.edu>
* Package name : waf Version : 1.9.5 Upstream Author : Thomas Nagy * URL : http://waf.io/ * License : BSD Programming Lang: Python Description : Tool for configuring, building, and installing projects Waf provides functionality similar to autotools (autoconf, automake, make). Waf build scripts are also valid python, so build scripts can easily use functionality from other python libraries to perform complex actions. --- I am trying to package waf because it is a build dependency for a few other packages I would like to package. I have a potential sponsor lined up for these, but I have to figure out the waf package first. There is a special note to packagers because waf tends to be included in compiled form with software sources. https://wiki.debian.org/UpstreamGuide#waf Doing a quick search curl -s https://codesearch.debian.net/results/22044ee2fe5c4350/packages.json | jq -r '.Packages[]' | wc -l shows 39 packages might also benefit from a central installation of waf. --- I currently have a setup that creates two packages: waf and python3-waflib. That means that the build scripts must be valid python 3. If needed, I could also make a python2-waflib. In that case, we might want to have different executables for python2 and python3. --- Waf has had a somewhat contentious history in Debian. It was packaged and then removed upon request by upstream. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580712 I have had a conversation with upstream (Thomas Nagy). Nagy still opposes a generic 'waf' package, but is fine with giving it a specific version number (e.g. waf-1.9.5). https://groups.google.com/d/msg/waf-users/T8f_-HW9_Tw/tuRk0IpIAQAJ I will defer to the consensus here on what to name the package and any executables.