So, I've got someone who asked about Subversion 1.6 for RHEL 4. I've found the old subversion-1.6.17-1.el4.1plos.src.rpm in this old thread ( http://www.svnforum.org/archive/index.php/t-40748.html) from mbaehr. And I should recognize it, it's partly based on Repoforge work I contributed to. And I'd already written a much cleaner 1.6.17 SRPM structure for Repoforge, but never bothered to submit it after Subversion 1.7.3 was released and I turned to that.
The more sophisticated Subversion gets, dependent on recent versions of ruby and Java and other build tools, the tougher maintaing that sort of update gets for old OS's. Does anyone have a need or desire for RHEL 4 compatible tools? Or since RHEL 4 is in "extended support", should it just be ignored (according to the Subverson community)? It's a real pain to build on such an older system: it requires a local build of Python (for a tiny little bit of configuration scripting, not for run-time use!), neon (which gets built locally and loaded statically), the sqlite-amalgamation toolkit (which is an old and well handled dependency for old OS's), and swig. But combine that with management of Java toolkits, Gnome and KDE Wallets, and the psvn incompatibility with older Emacs, and it's getting out of hand. Is it worth re-integrating to the main Repoforge codeline to support such an old OS? Or should it simply be ignored and the limited tool from mbauer left as authoritative?