Re: Packaging pypy

[Stefano Rivera <stefanor@debian.org>]

Hi debian-python (2011.12.23_13:44:44_+0200)
> ... so, I've spent some time on this, and have an incomplete package to
> show for it: http://anonscm.debian.org/gitweb/?p=users/stefanor/pypy.git

Spent a morning on it, and it seems to be working nicely now.

Test failures are almost all dealt with (on x86, haven't built anywhere
else, since I started).

Here's a hacked virtualenv that'll work with it (upstream virtualenv
doesn't expect pypy to use this install layout):
https://github.com/stefanor/virtualenv/tree/pypy

Please play with it, if you are interested. Or even better, review the
patches. I'm sure there are some lovely bugs waiting to be found :)

I ran the twisted test suite under it, and get 11 failures, compared to
8 with upstream's pypy 1.7 build.


The package name and directory is unversioned. I did that because it
uses PEP3147, and so packages using it shouldn't need to be rebuilt
unless they build C extensions. (And hopefully there'll only be a few of
those, cpyext is still rather incomplete).
Does anyone think I should have versioned it?

There are some debs here: http://people.debian.org/~stefanor/pypy/
(although they aren't from the cleanest build ever)
I've kicked off clean amd64 and i386 builds, and will upload the
results, when they are complete.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  H: +27 21 465 6908 C: +27 72 419 8559  UCT: x3127