First of all my apologies to all for hijacking an earlier thread to post my questions on this topic... I actually knew that you're not supposed to hit "Reply" on another thread and change the Subject but I had forgotten that.

I'll restate my question in this new thread, followed by a reply from Daniel Shahaf and a followup question.

The question I asked was:

Subversion installation is version 1.4.2 on CentOS 5.2.

Client is TortoiseSVN on Windows XP.

I am using ONLY the svn+ssh protocol. I am not using the web interface, nor am I accessing the repository locally on the Linux box.

Am I using any component of the Subversion installation on the CentOS 5.2 machine other than svnserve and the repository?

Daniel Shahaf replied: "Yes, the shared libs that svnserve uses. (see ldd(1))"

I went into /usr/bin and said "ldd ./svnserve" and got back quite an impressive list of shared libraries.

My question is, other than the ones with filenames that begin "libsvn", how many of those are specific to svnserve? I think that most of them are general-use libraries that are used by a lot of different programs that have nothing to do with Subversion.

Here is my problem. I am running a Subversion server using version 1.4.2, which is the version that is installed by default with CentOS 5.x. For reasons that have nothing to do with performance or reliability... it currently hosts almost 14,000 files and I've had exactly zero problems with it in the year and a half I've been running it on this project..., I am shortly going to be, shall we say, strongly encouraged to upgrade to a 1.6.x release like the latest stable. I need to do this in a way that's as simple and instantaneous as possible to revert back to 1.4.2 if I run into an issue.

I am (as far as I know) using only svnserve and svnadmin, not the local svn client or the web interface or anything else. So I'm wondering if I can just drop the svnserve out of 1.6.xx in place of the one in 1.4.2 and run with that, and put the one from 1.4.2 back if I have any problems.

I realize that that kind of thing virtually never works in the *nix world (or for that matter, in the Windoze world) where everything is dependent on a hundred other things. But I thought I'd ask, anyway.

Reply via email to