On Tue, 7 Feb 2012 13:16:01 +0000
Ian Jackson <ijackson@chiark.greenend.org.uk> wrote:
> Michael Biebl writes ("Doesn't contain source for waf binary code"):
> > as this issue affects quite a few packages, I'd like to bring this
> > up for wider discussion.
> >
> > The issue basically is, that the waf build system uses a python
> > script, which embeds a bz2 tarball containing further python
> > sources. Those are unpacked to .waf-*/ when the waf script is
> > executed. More details can be found at [1].
> * It is possible that some upstream "source" packages contain "waf"
> scripts which were generated from modified versions of waf.git. In
> this case we may discover that those packages cannot be built with
> publicly available versions of waf.git.
I don't know anything about waf not mentioned in this thread, but
would it be possible to patch the package to work with a packaged waf
instead?
thanks,
kk
--
Karl Goetz, (Kamping_Kaiser / VK7FOSS)
http://www.kgoetz.id.au
No, I won't join your social networking group
Attachment:
signature.asc
Description: PGP signature