On Mon, May 26, 2014 at 06:57:18AM +0200, Remi Pointel wrote:
> On Sun, 25 May 2014 23:00:35 +0200
> Landry Breuil <[email protected]> wrote:
>
> > On Sun, May 25, 2014 at 09:19:11PM +0100, Stuart Henderson wrote:
> > > On 2014/05/25 22:08, frantisek holop wrote:
> > > >
> > > > what is the timeline of flipping py3 flavour
> > > > over to python3.4?
> > >
> > > A bulk build was done with iirc minimal fallout .. but if it's going in
> > > this release cycle, it needs to be sooner rather than later.
> >
> > Yes, py3-cairo was failing, iirc rpointel@ is looking into this.
>
> Hi,
>
> this is the diff to build py3-cairo with Python 3.4.
>
> This patch works fine with Python 3.3 too.
I'll put it in a bulk, but i'll have a minor nit.
> +# du to the fact that waf extract embedded bzip2 tarball unpacked at runtime.
> +# we need to call waf to create files before patching files.
> +post-extract:
> + cd ${WRKSRC} && ${MODPY_BIN} ./waf --help 1>&2 > /dev/null
> + cd ${WRKSRC} && ln -s .waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6 waf3
use ln -s .waf3-* waf3 here to avoid having that stupid checksum ?
Landry
