Processed: retitle 654462 to Doesn't contain source for waf binary code ...
dr at jones.dk
Wed Jan 4 11:18:36 UTC 2012
On 12-01-04 at 10:37am, Daniel Svensson wrote:
> On Tue, Jan 3, 2012 at 11:03 PM, Debian Bug Tracking System
> <owner at bugs.debian.org> wrote:
> > Bug #654512 [xmms2] postler: doesn't contain source for waf binary code
> > Changed Bug title to 'Doesn't contain source for waf binary code' from 'postler: doesn't contain source for waf binary code'
> This is just a compressed file in the XMMS2 project. You can compress
> your own from this script and the configuration file:
> I don't believe the Debian package includes these two files, but the
> upstream source tar ball do.
> You can also use some external waf package if you wish so, but we
> cannot guarantee it will work as we usually pull in patches from
> upstream waf when we want to do things that isn't supported in the
> released version yet, or the upstream version has been changed and we
> rather get our software out with a working build system instead of
> spending a couple of weeks making sure the new version builds our
> software on all our supported OSes.
> As I mentioned, this is a question of a compressed file, so sure it's
> binary encoded, but when you execute ./waf, it will decompress into
> the ".waf-1.6.7-b271784c448ab906d5606267fb7f92c0" directory in the top
> level directory.
How can the Debian project rest assured that that the binary indeed is
(only!) unpacking itself when executed?
Also, that it is the case for _every_ new upstream release, not only
once when you cared to investigate closely.
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: Digital signature
More information about the pkg-multimedia-maintainers