On Tue, May 23, 2017 at 11:05 AM, Todd Armstrong
<todd.armstrong_at_newscycle.com> wrote:
> Cedric, Thanks for posting the bug details.
>
> We have been using Wandisco's releases and are quite thankful for them as when we started using subversion a couple of years ago RHEL version was so out of date even then that we couldn't really justify starting with what they ship when 1.8 branch had so many improvements in it.
>
> The RHEL position has some merit, but given the advances between what they are shipping and what is currently available they sound a lot more to me like excellent reasons to ship svn17, svn18, svn19, etc. and use the availability of higher version as a means to make it possible (and push) their customers towards more current releases - seems like that could allow them to stay more current on each version level branch and reduce backporting of fixes to older versions by pointing those looking for them to newer versions that already have them and are available as part of RHEL.
Agreed, except for the dependency trees for building more recent
versions of Subversion on, say, RHEL 6 or RHEL 7. I'm reviewing my old
efforts at https://github.com/nkadel/, and I finally had to throw in
the towel because of critical security component dependencies, where
upgrading them enough for Subversion 1.9 would break existing
libraries or requre parallel installing *those*. It got out of hand.
Puttin gthem in the "sclo" repositories, installed over in
/opt/rh/svn19/, would allow including those updated libraries there as
well. It's just a lot of work, and no one's offered me money to try,
so I've personally not pursued it.
Received on 2017-05-24 05:21:10 CEST