Alexander Reichle-Schmehl writes ("Re: Doesn't contain source for waf binary
code"):
> However, regarding that specific point: waf once was packaged in
> Debian. See <20100227195857.07540195@utumno>
> (http://lists.debian.org/debian-devel/2010/02/msg00714.html) for details
> about the removal.
Hi!
Am 07.02.2012 14:16, schrieb Ian Jackson:
> * Upstream waf should be packaged somehow. Upstream's declared
>policy of asking packages to ship a copy of waf suggests that there
>won't be much API stability so we will need to encode the waf
>version number in the package name, an
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 so
Hi,
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
4 matches
Mail list logo
