On Wed, Jan 4, 2012 at 12:52 PM, Jonas Smedegaard <[email protected]> wrote: > On 12-01-04 at 12:42pm, Daniel Svensson wrote: >> On Wed, Jan 4, 2012 at 12:34 PM, Jonas Smedegaard <[email protected]> wrote: >> > I believe you did not answer my question: I did not ask how the >> > Debian project can verify later on, but how it can rest assured that >> > this verification have already been done for packages using waf. >> >> Which is why I mentioned it's 1.6.7 vanilla waf, which can be >> downloaded and used instead of the bundled version, or perhaps >> packaged and added as a source dependency. > > "which is why" is a diversion, not an answer.
This was not my intention and I'm truly sorry you feel this way. My apologies. Here is a link to the version of Waf I'm referring to: http://code.google.com/p/waf/downloads/detail?name=waf-1.6.7 It can be used as a replacement for the compressed version. Here are two options I can think of: * Add the above mentioned source code to the Debian git repositories each project in question and remove the upstream compressed versions. * ...or, package waf and add it as a source dependency for the affected packages. And the second option is not really an option due to: http://lists.debian.org/debian-devel/2010/02/msg00714.html My 2 cents at least. -- Daniel Svensson _______________________________________________ Pkg-crosswire-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
