RE: Subversion on RedHat
From: Cedric J.F. Blomart (MINFIN) <cedric.blomart_at_minfin.fed.be>
Date: Tue, 23 May 2017 11:50:50 +0000
RedHat is already evaluating is releasing a newer version of subversion is feasible in RHSCL (software collection). If anyone has the issue and support from redhat I think they should submit their case into #Bug 1162551.
Concerning version concurrency (client, server, build system), the only good solution is communication between the different parties.
-----Message d'origine-----
On Tue, May 23, 2017 at 5:00 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
Yup! You would.
It would be feasible to talk RHEL into adding an "sclo", or software collections library, version of Subversion over in /opt/rh/svn19/. It would pretty much guarantee emotional angst when the default Subversion 1.6.x was used on a working repository that was checked out with 1.9.x. If RHEL or a local admin swapped the default or reset the default on a Jenkins build environment, for example, I'd personally be quite upset.
It would also be feasible to build an alternative package named "subvesion19", much as they used to publish multiple versions of gcc as gcc33, gcc44, etc. on the same system. So it's possible. But it's work. And I'll admit that frankly, RHEL 6 is getting a bit long in the tooth. And even git is suffering similar issues of being seriously out of date for the commercial releases of RHEL, so Subversion is not the only source control system suffering from this problem.
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.