Hi Michael, Michael Guntsche wrote:
Stefan Behnel writes:
Here, it's actually sufficient to checkout the "Pyrex" directory under the lxml source tree, i.e.
svn co http://codespeak.net/svn/lxml/trunk lxml cd lxml svn co http://codespeak.net/svn/lxml/pyrex/Pyrex Pyrex
That has the additional advantage that you can "svn up" both with a single command.
You need to edit the svn:externals property so Pyrex gets updated as well. You can do the following.
svn co http://codespeak.net/svn/lxml/trunk lxml svn ps svn:externals "Pyrex http://codespeak.net/svn/lxml/pyrex/Pyrex" lxml svn up lxml
This way everything gets updated, when you do a "svn up". Maybe it makes sense to put svn:externals in trunk, since people who checkout from trunk need Pyrex anyway.
I was always hoping we could get back to depending on a normal Pyrex release rather sooner than later, but I guess you're right. Since Greg doesn't follow a very open project management style, it's hard to predict when lxml will be able to build with an unpatched Pyrex release. I'll go with the above for now... Stefan