> 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.
