On Tue, Aug 26, 2008 at 02:10:03AM +0300, Valery Masiutsin wrote: > Hello, guys ! > > Here is an updated diff. > What was done: > WRKBUILD variable has been added to make flags, i've patched some of > python scripts to use it, now most of tests in do-regress target pass > fine, however i did not check them all yet.
The bindings tests pass for you? Do you see any errors like I described here? http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=142053 If not, the failing tests I'm seeing could be a local problem on my machine :/ > Everything builds and packages fine for me on amd64 with > SEPARATE_BUILD=Yes. I'd rather not use SEPARATE_BUILD, if not using it means less patches to maintain. It does not seem mandatory to use SEPARATE_BUILD. From bsd.port.mk(5): SEPARATE_BUILD Many GNU configure ports can be built in a directory dis- tinct from the place they were unpacked. For some specific ports, this is even mandatory. Set to `simple' if this is the case. As I read this, it says "use SEPARATE_BUILD if you want to use it, or if it's really needed". Which isn't the case for us, right? We could eventually start using SEPARATE_BUILD again once the issues are fixed upstream. Also, Valery, if you want to pick up maintainership for this port (i.e. maintain it in the long term), please feel free to do so. I put my name into MAINTAINER in my patch mostly because the CVS logs show timeouts by the old maintainer (Sigfried, in Cc), and because I felt sort of obligated to keep maintaining the port if no one else wants it (being one of the few people who are Subversion developers and OpenBSD users at the same time). So I would be glad if you took official maintenance for this port. I will be around to help wherever and whenever I can, of course :) But if this is too much of a burden for you (or if it turns out to be at some point), I can take the port and keep updating it, no problem. Since Sigfried has not been doing active maintenance of the port for some time, I expect we can assume that he is fine with handing maintainership over to someone else. Also note that 1.5.2 is due being rolled on Wednesday, and should be released on the following weekend if things go as planned. Thanks, Stefan
