version control the pyrex output files

I agree :) Mind you I argued for versioning them in the first place.

Barry isn't the first user I've seen with this issue - tracking bzr.dev
and running it to help us (on a server where .debs isn't appropriate). I
think we should revisit this.

-Rob

On Mon, 2009-03-02 at 22:02 +0000, John A Meinel wrote:
> ** Changed in: bzr
> Importance: Undecided => Wishlist
> Status: New => Triaged

Wishlist indicates we'll do it if someone puts the effort in :) What
would be needed to make this acceptable?

-Rob

2009/3/3 Robert Collins <email address hidden>:
> On Mon, 2009-03-02 at 22:02 +0000, John A Meinel wrote:
>> ** Changed in: bzr
>>    Importance: Undecided => Wishlist
>>        Status: New => Triaged
>
> Wishlist indicates we'll do it if someone puts the effort in :) What
> would be needed to make this acceptable?

I have no objection any more; we're not changing them all that often
and I can see how it would help barry.

--
Martin <http://launchpad.net/~mbp/>

The only problem I have with that is that different versions of pyrex are used across the team.

We should at least decide which one must be used or we may have silly conflicts (John pointed out that I used an old pyrex version when I had to re-recreate the 1.12 tar ball).