Bug 19759

Summary:	wscripts incompatible with waf 1.5
Product:	Telepathy	Reporter:	Jasper Lievisse Adriaanse <jasper>
Component:	butterfly	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	olivier.crete
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Attachments:	as committed into openbsd

Description Jasper Lievisse Adriaanse 2009-01-27 00:23:42 UTC

Created attachment 22267 [details] [review]
as committed into openbsd

the wscripts in that are being shipped with telepathy-butterfly, are incompatible with waf 1.5.2, hence causing the build to fail.

this was fixed in openbsd ports recently by rewriting some parts of the wscripts.
patches were done by Landry Breuil (landry@openbsd.org).

Comment 1 Jonny Lamb 2009-02-04 08:52:39 UTC

Thanks for your patch.

Unfortunately, I don't know anything about waf. While skimming the patch, I have one question:

+        obj.install_path = os.path.join('/usr/local/lib/python2.5/site-packages/butterfly', loc)

This appears to hardcode the prefix to /usr/local/. Is there no way to make that more customisable?

Comment 2 Olivier Crête 2009-08-07 20:44:29 UTC

Waf isn't great at all.. Maybe we should just move to something more appropriate like distutils..

Comment 3 Olivier Crête 2009-08-07 20:45:10 UTC

see https://bugs.gentoo.org/show_bug.cgi?id=233948
it seems to build .pyo/.pyc files.. but does not install them...

Comment 4 Simon McVittie 2009-08-11 06:11:45 UTC

(In reply to comment #2)
> something more appropriate like distutils..

Note that telepathy-python just moved from distutils to autotools, because we've had at least two broken releases in which distutils inexplicably omitted a file from the tarball. I would not recommend distutils.

Comment 5 Olivier Le Thanh Duong 2010-03-12 15:34:56 UTC


*** This bug has been marked as a duplicate of bug 27053 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.