On Wed, Mar 11, 2020 at 10:25 AM Michael Pilato <cmpil...@collab.net> wrote:
> > While you're waiting for someone to manually roll a nightly tarball, can > we > > circle back to the original problem for a minute: What stops you from > > running autogen.sh? Is it just that you'd like someone to figure out > > the list of build dependency package names and configure arguments for > > a working copy build for your platform? (Note this could be a concern > > even for tarball builds, if both py2 and py3 are installed.) > > So, yes, I "just" need a functional 1.14-to-be Subversion with Python 3 > bindings for the purposes of testing my attempts to convert ViewVC itself > to Python 3. But I'd also like to get a head start on getting some of this > working in CollabNet's public and private ecosystems, which depend on > having a Subversion release tarball as their starting block. My request > was aimed at hopefully meeting all of those needs simultaneously. There's also the makefile in tools/dev/unix-build. It sets up a development working copy, downloads and builds all the dependencies, and can run all tests with all back ends and repo access layers. It is used on the OpenBSD buildbot and I successfully used it on the latest Debian (though I've had to install some -dev versions of some Debian packages, and change a few versions of downloaded dependencies -- if interested, look for a dev@ thread titled "Makefile.svn: a dumb question" in December 2019 where among other things I sent some patches for this makefile). I'm away from my computer right now but if you go this route I'll be happy to help as much as possible. Cheers, Nathan
